Bug 1303269
Summary: | After GlusterD restart, Remove-brick commit happening even though data migration not completed. | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Atin Mukherjee <amukherj> | |
Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bsrirama, bugs, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1303125 | |||
: | 1310972 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:56:06 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: | 1303028, 1303125, 1311041 | |||
Bug Blocks: | 1310972 |
Description
Atin Mukherjee
2016-01-30 03:15:51 UTC
REVIEW: http://review.gluster.org/13323 (glusterd: set decommission_is_in_progress flag for inprogress remove-brick op on glusterd restart) posted (#1) for review on master by Atin Mukherjee (amukherj) REVIEW: http://review.gluster.org/13323 (glusterd: set decommission_is_in_progress flag for inprogress remove-brick op on glusterd restart) posted (#2) for review on master by Atin Mukherjee (amukherj) REVIEW: http://review.gluster.org/13323 (glusterd: set decommission_is_in_progress flag for inprogress remove-brick op on glusterd restart) posted (#3) for review on master by Atin Mukherjee (amukherj) COMMIT: http://review.gluster.org/13323 committed in master by Atin Mukherjee (amukherj) ------ commit 3ca140f011faa9d92a4b3889607fefa33ae6de76 Author: Atin Mukherjee <amukherj> Date: Sat Jan 30 08:47:35 2016 +0530 glusterd: set decommission_is_in_progress flag for inprogress remove-brick op on glusterd restart While remove brick is in progress, if glusterd is restarted since decommission flag is not persisted in the store the same value is not retained back resulting in glusterd not blocking remove brick commit when rebalance is already in progress. Change-Id: Ibbf12f3792d65ab1293fad1e368568be141a1cd6 BUG: 1303269 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/13323 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Gaurav Kumar Garg <ggarg> Reviewed-by: mohammed rafi kc <rkavunga> 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |