[Bugs] [Bug 1446172] Brick Multiplexing : - resetting a brick bring down other bricks with same PID

bugzilla at redhat.com bugzilla at redhat.com
Wed May 10 18:58:24 UTC 2017


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



--- Comment #6 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17128 committed in master by Jeff Darcy
(jeff at pl.atyp.us) 
------
commit 74383e3ec6f8244b3de9bf14016452498c1ddcf0
Author: Samikshan Bairagya <samikshan at gmail.com>
Date:   Mon Apr 24 22:00:17 2017 +0530

    glusterd: Make reset-brick work correctly if brick-mux is on

    Reset brick currently kills of the corresponding brick process.
    However, with brick multiplexing enabled, stopping the brick
    process would render all bricks attached to it unavailable. To
    handle this correctly, we need to make sure that the brick process
    is terminated only if brick-multiplexing is disabled. Otherwise,
    we should send the GLUSTERD_BRICK_TERMINATE rpc to the respective
    brick process to detach the brick that is to be reset.

    Change-Id: I69002d66ffe6ec36ef48af09b66c522c6d35ac58
    BUG: 1446172
    Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
    Reviewed-on: https://review.gluster.org/17128
    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=FRI6j4yuOy&a=cc_unsubscribe


More information about the Bugs mailing list