Bug 1044337
Summary: | Error while executing action CommitRemoveGlusterVolumeBricks: Command execution failed return code: 146 | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Vijaikumar Mallikarjuna <vmallika> |
Component: | glusterd | Assignee: | Vijaikumar Mallikarjuna <vmallika> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | mainline | CC: | barumuga, bturner, bugs, dpati, dtsang, gluster-bugs, knarra, lmohanty, mmahoney, pprakash, rhs-bugs, smohan, ssampat, vbellur, vmallika |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | 1019908 | Environment: | |
Last Closed: | 2014-11-11 08:25:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1019908 | ||
Bug Blocks: |
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 (#2) for review on master by Vijaikumar Mallikarjuna (vmallika) 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> 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/ 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 |