Bug 1044337 - Error while executing action CommitRemoveGlusterVolumeBricks: Command execution failed return code: 146
Summary: Error while executing action CommitRemoveGlusterVolumeBricks: Command executi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard:
Depends On: 1019908
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 06:46 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:47 UTC (History)
15 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Doc Type: Bug Fix
Doc Text:
Cause: replace-brick was hanging and after sometime CLI command is disconnected from glusterd with ECONNREFUSED(146) error. This is because glusterd was going into deadlock after sending commit acknowledgement to other nodes in the cluster. Fix: Hold the big-lock before send any acknowledgement to another node within the cluster Result: replace-brick should not hang and should return success.
Clone Of: 1019908
Environment:
Last Closed: 2014-11-11 08:25:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 1 Anand Avati 2013-12-18 07:13:32 UTC 
REVIEW: http://review.gluster.org/6534 (glusterd: hold the lock when submitting ACC in replace-brick) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
Comment 2 Anand Avati 2013-12-19 05:56:22 UTC 
REVIEW: http://review.gluster.org/6534 (glusterd: hold the lock when submitting ACC in replace-brick) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
Comment 3 Anand Avati 2013-12-19 11:55:42 UTC 
COMMIT: http://review.gluster.org/6534 committed in master by Vijay Bellur (vbellur) 
------
commit e22c42d9154c2d9090149003038f38164701dc08
Author: Vijaykumar M <vmallika>
Date:   Wed Dec 18 12:38:26 2013 +0530

    glusterd: hold the lock when submitting ACC in replace-brick
    
    replace-brick handler sets the timer to perform the replace operation and unlocks the big_lock.
    So we need to lock inside 'glusterd_do_replace_brick' before submitting the ACC
    
    Change-Id: I5525c62533bd92d3ac46587e5353e2443ad85851
    BUG: 1044337
    Signed-off-by: Vijaykumar M <vmallika>
    Reviewed-on: http://review.gluster.org/6534
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>
Comment 4 Niels de Vos 2014-09-22 12:33:55 UTC 
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/
Comment 5 Niels de Vos 2014-11-11 08:25:52 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users
Note You need to log in before you can comment on or make changes to this bug.