Bug 961342

Summary:	[FEAT] Start gsyncd on only one node of a replica pair
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	glusterd	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	gluster-bugs, ndevos
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-11 16:06:17 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 Avra Sengupta 2013-05-09 12:53:10 UTC

Description of problem:
gsyncd should start on only one node of a replica pair. If the node goes down, doing a geo-rep start force should spawn gsyncd on the other node of the replica pair.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Avra Sengupta 2014-04-09 10:42:19 UTC

Fix at http://review.gluster.org/#/c/5132/

Comment 2 Niels de Vos 2014-07-11 16:06:17 UTC


*** This bug has been marked as a duplicate of bug 847839 ***