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

[bugzilla at redhat.com]

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



--- Comment #11 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16532 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit da30f79c9e35ab8cca71601a33665af72d0880ff
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.

    Backport of:
    > Change-Id: I098465b175ecf23538bd7207357c752a2bba8f4e
    > BUG: 1385758
    > Reviewed-on: https://review.gluster.org/16509

    BUG: 1418091
    Change-Id: Ia61e273134520c8ccfa3371ee2370cb9a1920877
    Signed-off-by: Jeff Darcy <jdarcy at redhat.com>
    Reviewed-on: https://review.gluster.org/16532
    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: Shyamsundar Ranganathan <srangana at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.