Bug 820428

Summary:	[RFE] Geo-replication is not automatically restarted on remaining Masters
Product:	[Community] GlusterFS	Reporter:	Andreas Kurz <andreas>
Component:	geo-replication	Assignee:	Csaba Henk <csaba>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	avishwan, bugs, gluster-bugs, rwheeler, vbellur
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-09 11:05:58 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:

Description Andreas Kurz 2012-05-09 22:05:57 UTC

Description of problem:

Starting geo-replication on a replicated volume only ever starts the gsyncd processes on the node where the command was executed. There is no automatic restard of geo-replication in case that node dies.
 
Version-Release number of selected component (if applicable):

3.2.6

How reproducible:

Always

Steps to Reproduce:
1. start geo-replication on node1
2. reset node1
3. check geo-replication status on remaining node
  
Actual results:

Geo-replication is not running

Expected results:

Geo-replication is running

Comment 1 Niels de Vos 2014-11-27 14:45:10 UTC

Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.

Comment 2 Aravinda VK 2015-04-09 11:05:58 UTC

This is not applicable with the Distributed Geo-replication from >3.5. Closing this bug. Please reopen if issue found again.