Bug 1049727
| Summary: | Dist-geo-rep : volume won't be able to stop untill the geo-rep session is deleted. | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Kotresh HR <khiremat> |
| Component: | geo-replication | Assignee: | Kotresh HR <khiremat> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | pre-release | CC: | aavati, bbandari, csaba, gluster-bugs, khiremat, rhs-bugs, vagarwal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.5.2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1002822 | Environment: | |
| Last Closed: | 2014-09-16 19:44:26 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: | 1002822, 1170048, 1176824, 1179638, 1186707 | ||
| Bug Blocks: | |||
|
Comment 1
Anand Avati
2014-01-08 05:29:06 UTC
REVIEW: http://review.gluster.org/6663 (glusterd/geo-rep : Allow volume to stop if geo-rep is not active.) posted (#2) for review on master by Kotresh HR (khiremat) REVIEW: http://review.gluster.org/6663 (glusterd/geo-rep : Allow volume to stop if geo-rep is not active.) posted (#3) for review on master by Kotresh HR (khiremat) COMMIT: http://review.gluster.org/6663 committed in master by Vijay Bellur (vbellur) ------ commit 2f499e85a4ae0ac1e84785daa60a5bbfe979cc7f Author: Kotresh H R <khiremat> Date: Wed Jan 8 10:52:28 2014 +0530 glusterd/geo-rep : Allow volume to stop if geo-rep is not active. In staging phase of volume stop, code is added to read the state_file for each slave of the master to which the volume belongs. If any of the geo-rep session is active with at least one slave, volume is not allowed to stop else it is allowed. Change-Id: I4a01a357fc86b872e9635b3d19998cdbd9545114 BUG: 1049727 Signed-off-by: Kotresh H R <khiremat> Reviewed-on: http://review.gluster.org/6663 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur> REVIEW: http://review.gluster.org/6821 (glusterd/geo-rep : Allow volume to stop if geo-rep is not active.) posted (#1) for review on release-3.5 by Kotresh HR (khiremat) COMMIT: http://review.gluster.org/6821 committed in release-3.5 by Vijay Bellur (vbellur) ------ commit 870ea37dcd440b33418bab5c9e2c69ca67bb668e Author: Kotresh H R <khiremat> Date: Wed Jan 8 10:52:28 2014 +0530 glusterd/geo-rep : Allow volume to stop if geo-rep is not active. In staging phase of volume stop, code is added to read the state_file for each slave of the master to which the volume belongs. If any of the geo-rep session is active with at least one slave, volume is not allowed to stop else it is allowed. Change-Id: I4a01a357fc86b872e9635b3d19998cdbd9545114 BUG: 1049727 Signed-off-by: Kotresh H R <khiremat> Reviewed-on: http://review.gluster.org/6663 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/6821 REVIEW: http://review.gluster.org/7028 (mgmt/glusterd: Improve log message strings.) posted (#1) for review on master by Vijay Bellur (vbellur) REVIEW: http://review.gluster.org/7028 (mgmt/glusterd: Improve log message strings.) posted (#2) for review on master by Kotresh HR (khiremat) REVIEW: http://review.gluster.org/7028 (mgmt/glusterd: Improve log message strings.) posted (#3) for review on master by Kotresh HR (khiremat) 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.5.2, please reopen this bug report. glusterfs-3.5.2 has been announced on the Gluster Users mailinglist [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-July/041217.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |