Bug 764269 (GLUSTER-2537)

Summary:	gsync autorestart
Product:	[Community] GlusterFS	Reporter:	Csaba Henk <csaba>
Component:	geo-replication	Assignee:	Csaba Henk <csaba>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, kbudiger, lakshmipathi, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTA	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Csaba Henk 2011-03-16 18:59:07 UTC

We should support an autorestart mode for georeplication so that if the synchronization is interrupted due to some external circumstances (eg. network goes down), then it shall be reestablished without user intervention.

Comment 1 Vijay Bellur 2011-04-04 12:02:25 UTC

PATCH: http://patches.gluster.com/patch/6693 in master (syncdaemon: provide transactional semantics to config file writing)

Comment 2 Vijay Bellur 2011-04-04 12:02:29 UTC

PATCH: http://patches.gluster.com/patch/6694 in master (syncdaemon: add monitor mode to support autorestart)

Comment 3 Lakshmipathi G 2011-04-15 12:15:25 UTC

killed gsyncd.py process - monitor restarts it again. - tested with 3.2.0qa12

Comment 4 Anand Avati 2011-05-09 17:27:02 UTC

PATCH: http://patches.gluster.com/patch/7095 in master (syncdaemon: some refactor on monitor)

Comment 5 Lakshmipathi G 2011-05-31 10:21:46 UTC

tested with above patch with 3.2.0

Comment 6 Anand Avati 2011-05-31 14:01:44 UTC

PATCH: http://patches.gluster.com/patch/7343 in release-3.2 (syncdaemon: some refactor on monitor)