Bug 1159209 - Geo-Replication Passive node is not getting promoted to active when one node of replicated slave volume goes down
Summary: Geo-Replication Passive node is not getting promoted to active when one node ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.6.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On: 1126798 1151412 1152990 1182888
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-31 08:45 UTC by Aravinda VK
Modified: 2015-05-18 10:47 UTC (History)
13 users (show)

Fixed In Version: glusterfs-3.6.3beta1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1151412
Environment:
Last Closed: 2015-05-18 10:47:17 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-10-31 08:50:11 UTC
REVIEW: http://review.gluster.org/9025 (geo-rep: Failover when a Slave node goes down) posted (#1) for review on release-3.6 by Aravinda VK (avishwan)

Comment 2 Anand Avati 2014-11-13 06:22:57 UTC
COMMIT: http://review.gluster.org/9025 committed in release-3.6 by Venky Shankar (vshankar) 
------
commit 085e70e15194c71cdbee6f6683ff7e718558bf1f
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: 1159209
    Change-Id: I7ca2a66ff2a438435f297b7063313214c28f3d4b
    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>
    Reviewed-on: http://review.gluster.org/9025

Comment 3 Aravinda VK 2015-05-18 10:47:17 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.