[Bugs] [Bug 1159209] Geo-Replication Passive node is not getting promoted to active when one node of replicated slave volume goes down
bugzilla at redhat.com
bugzilla at redhat.com
Thu Nov 13 06:22:57 UTC 2014
https://bugzilla.redhat.com/show_bug.cgi?id=1159209
--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9025 committed in release-3.6 by Venky
Shankar (vshankar at redhat.com)
------
commit 085e70e15194c71cdbee6f6683ff7e718558bf1f
Author: Aravinda VK <avishwan at redhat.com>
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: 1159209
Change-Id: I7ca2a66ff2a438435f297b7063313214c28f3d4b
Signed-off-by: Aravinda VK <avishwan at redhat.com>
Reviewed-on: http://review.gluster.org/8921
Reviewed-by: Kotresh HR <khiremat at redhat.com>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Venky Shankar <vshankar at redhat.com>
Tested-by: Venky Shankar <vshankar at redhat.com>
Reviewed-on: http://review.gluster.org/9025
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=8TWOanrUlB&a=cc_unsubscribe
More information about the Bugs
mailing list