Bug 1151412
| Summary: | Geo-Replication Passive node is not getting promoted to active when one node of replicated slave volume goes down | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Aravinda VK <avishwan> | |
| Component: | geo-replication | Assignee: | Aravinda VK <avishwan> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | mainline | CC: | aavati, avishwan, bugs, csaba, jcastillo, khiremat, ndevos, nlevinki, nsathyan, storage-qa-internal, vumrao | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.7.0beta1 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1126798 | |||
| : | 1159209 (view as bug list) | Environment: | ||
| Last Closed: | 2015-05-14 17:26:15 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: | 1126798, 1152990, 1182888 | |||
| Bug Blocks: | 1159209 | |||
|
Comment 1
Anand Avati
2014-10-10 10:53:36 UTC
REVIEW: http://review.gluster.org/8921 (geo-rep: Failover when a Slave node goes down) posted (#2) for review on master by Aravinda VK (avishwan) REVIEW: http://review.gluster.org/8921 (geo-rep: Failover when a Slave node goes down) posted (#3) for review on master by Aravinda VK (avishwan) REVIEW: http://review.gluster.org/8921 (geo-rep: Failover when a Slave node goes down) posted (#4) for review on master by Aravinda VK (avishwan) REVIEW: http://review.gluster.org/8921 (geo-rep: Failover when a Slave node goes down) posted (#5) for review on master by Aravinda VK (avishwan) REVIEW: http://review.gluster.org/8921 (geo-rep: Failover when a Slave node goes down) posted (#6) for review on master by Aravinda VK (avishwan) REVIEW: http://review.gluster.org/8921 (geo-rep: Failover when a Slave node goes down) posted (#7) for review on master by Aravinda VK (avishwan) COMMIT: http://review.gluster.org/8921 committed in master by Venky Shankar (vshankar) ------ commit 2d92565e60485c81bbe6b3ebde60aeb623eda36a Author: Aravinda VK <avishwan> Date: Fri Oct 10 16:13:25 2014 +0530 geo-rep: Failover when a Slave node goes down When a slave node goes down, worker in master node can connect to different slave node and resume the operation. Existing georep was not checking the status of slave node before worker restart. With this patch, geo-rep worker will check the node status using `gluster volume status` when it goes faulty. BUG: 1151412 Change-Id: If3ab7fdcf47f5b3f3ba383c515703c5f1f9dd668 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/8921 Reviewed-by: Kotresh HR <khiremat> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar> Tested-by: Venky Shankar <vshankar> REVIEW: http://review.gluster.org/9432 (geo-rep: Handle Volume status error while getting slave nodes) posted (#1) for review on master by Aravinda VK (avishwan) COMMIT: http://review.gluster.org/9432 committed in master by Venky Shankar (vshankar) ------ commit 015282013a22dda84d1849e18659d42bb5bb48f4 Author: Aravinda VK <avishwan> Date: Mon Jan 12 12:19:17 2015 +0530 geo-rep: Handle Volume status error while getting slave nodes gluster volume status command not returns xml output, when any error like "Transaction in Progress", we need to handle returncode along with xml error. BUG: 1151412 Signed-off-by: Aravinda VK <avishwan> Change-Id: Id5b7712df7cff58744b4c5a0d00870aec1d926a8 Reviewed-on: http://review.gluster.org/9432 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Venky Shankar <vshankar> Tested-by: Venky Shankar <vshankar> 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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user 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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |