[Bugs] [Bug 1385758] [RFE] Support multiple bricks in one process (multiplexing)

bugzilla at redhat.com bugzilla at redhat.com
Thu Feb 2 17:35:05 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1385758



--- Comment #89 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16509 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 72452e07fcf91627afb6d45b921dfefd2610686f
Author: Jeff Darcy <jdarcy at redhat.com>
Date:   Wed Feb 1 21:54:30 2017 -0500

    glusterd: double-check whether brick is alive for stats

    With multiplexing, our tests detach bricks from their host processes
    without glusterd being involved.  Thus, when we ask glusterd to fetch
    profile info, it will try to fetch from a brick that's actually not
    present any more.  While it can handle the process being dead and its
    RPC connection being closed, it barfs if it gets a negative response
    from a live brick process.  This is not a problem in normal use,
    because the brick can't disappear without glusterd seeing it.  The fix
    is to double check that the brick is actually running, by looking for
    its pidfile which the tests *do* clean up as part of killing a brick.

    Change-Id: I098465b175ecf23538bd7207357c752a2bba8f4e
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy at redhat.com>
    Reviewed-on: https://review.gluster.org/16509
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=CpCYL3bV1d&a=cc_unsubscribe


More information about the Bugs mailing list