Bug 1454612 - glusterd on a node crashed after running volume profile command
Summary: glusterd on a node crashed after running volume profile command
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Gaurav Yadav
QA Contact:
URL:
Whiteboard:
Depends On: 1452956
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-23 07:43 UTC by Gaurav Yadav
Modified: 2017-05-30 18:53 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.11.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1452205
Environment:
Last Closed: 2017-05-30 18:53:12 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2017-05-25 15:14:03 UTC
REVIEW: https://review.gluster.org/17362 (glusterd : volume profile command on one of the node crashes glusterd) posted (#2) for review on release-3.11 by Gaurav Yadav (gyadav)

Comment 2 Worker Ant 2017-05-25 15:31:58 UTC
COMMIT: https://review.gluster.org/17362 committed in release-3.11 by Shyamsundar Ranganathan (srangana) 
------
commit a80ec1b99309ca113cd673d2bc0cf20d50822a47
Author: Gaurav Yadav <gyadav>
Date:   Sun May 21 12:31:29 2017 +0530

    glusterd : volume profile command on one of the node crashes glusterd
    
    When volume profile command is issued on one of the node glusterd
    crashes. Its a race condition which may hit when profile command and
    status command is being executed from node A and node B respectively.
    While doing so event GD_OP_STATE_BRICK_OP_SENT/GD_OP_STATE_BRICK_COMMITTED
    is being triggered. As handling of event is not thread safe, hence context
    got modify and glusterd crashes.
    
    With the fix now we are validating the context before using it.
    
    > Reviewed-on: https://review.gluster.org/17350
    > Smoke: Gluster Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > Reviewed-by: Samikshan Bairagya <samikshan>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>
    (cherry picked from commit 8dc63c8824fc1a00c873c16e8a16a14fca7c8cca)
    
    Change-Id: Ic07c3cdc5644677b0e40ff0fac6fcca834158913
    BUG: 1454612
    Signed-off-by: Gaurav Yadav <gyadav>
    Reviewed-on: https://review.gluster.org/17362
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>

Comment 3 Shyamsundar 2017-05-30 18:53:12 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.11.0, please open a new bug report.

glusterfs-3.11.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-May/000073.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.