Bug 1446172 - Brick Multiplexing :- resetting a brick bring down other bricks with same PID
Summary: Brick Multiplexing :- resetting a brick bring down other bricks with same PID
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Samikshan Bairagya
QA Contact:
URL:
Whiteboard: brick-multiplexing
Depends On:
Blocks: 1443843 1449933 1449934
TreeView+ depends on / blocked
 
Reported: 2017-04-27 11:42 UTC by Samikshan Bairagya
Modified: 2017-10-26 14:37 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.12.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1443843
: 1449933 1449934 (view as bug list)
Environment:
Last Closed: 2017-09-05 17:27:45 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Worker Ant 2017-04-27 11:53:23 UTC 
REVIEW: https://review.gluster.org/17128 (glusterd: Make reset-brick work correctly if brick-mux is on) posted (#1) for review on master by Samikshan Bairagya (samikshan)
Comment 2 Worker Ant 2017-05-09 04:57:49 UTC 
REVIEW: https://review.gluster.org/17128 (glusterd: Make reset-brick work correctly if brick-mux is on) posted (#2) for review on master by Samikshan Bairagya (samikshan)
Comment 3 Worker Ant 2017-05-10 04:45:06 UTC 
REVIEW: https://review.gluster.org/17128 (glusterd: Make reset-brick work correctly if brick-mux is on) posted (#3) for review on master by Samikshan Bairagya (samikshan)
Comment 4 Worker Ant 2017-05-10 05:36:33 UTC 
REVIEW: https://review.gluster.org/17128 (glusterd: Make reset-brick work correctly if brick-mux is on) posted (#4) for review on master by Samikshan Bairagya (samikshan)
Comment 5 Worker Ant 2017-05-10 12:09:30 UTC 
REVIEW: https://review.gluster.org/17128 (glusterd: Make reset-brick work correctly if brick-mux is on) posted (#5) for review on master by Samikshan Bairagya (samikshan)
Comment 6 Worker Ant 2017-05-10 18:58:24 UTC 
COMMIT: https://review.gluster.org/17128 committed in master by Jeff Darcy (jeff.us) 
------
commit 74383e3ec6f8244b3de9bf14016452498c1ddcf0
Author: Samikshan Bairagya <samikshan>
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>
    Reviewed-on: https://review.gluster.org/17128
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>
Comment 7 Shyamsundar 2017-09-05 17:27:45 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.12.0, please open a new bug report.

glusterfs-3.12.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-September/000082.html
[2] https://www.gluster.org/pipermail/gluster-users/
Note You need to log in before you can comment on or make changes to this bug.