Bug 1102524

Summary:	Dist-geo-rep : geo-rep resume after 120 sec of pause, would make geo-rep faulty and restarts instead of resuming.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	geo-replication	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rhgs-3.0	CC:	asriram, avishwan, chrisw, csaba, david.macdonald, mzywusko, nlevinki, sankarshan, smohan
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	usability
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	The Geo-replication worker goes to faulty state and restarts when resumed. It works as expected when it is restarted, but takes more time to synchronize compared to resume.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-16 15:58:16 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:
Bug Depends On:
Bug Blocks:	1087818

Description Vijaykumar Koppad 2014-05-29 06:43:17 UTC

Description of problem: geo-rep resume after 120 sec of pause, would restart geo-rep instead of resuming.


Version-Release number of selected component (if applicable): glusterfs-3.6.0.9-1.el6rhs


How reproducible: Happens everytime.


Steps to Reproduce:
1. create and start a geo-rep relationship between master and slave. 
2. start creating data on master.
3. Pause the geo-rep for more than 120 sec and resume it.
4. Check the status of the geo-rep 

Actual results: geo-rep goes to faulty for some time.


Expected results: when resumed, it should actually resume syncing, not restarting the geo-rep.


Additional info:

Comment 2 Nagaprasad Sathyanarayana 2014-06-05 07:22:49 UTC

As agreed by Dev leads, QE and PM, moving the BZ to future release.  The issue is not severe as sync of files resumes from the last checkpoint and it does not crawl the entire file system.

Comment 3 Shalaka 2014-06-27 11:11:49 UTC

Please review and signoff edited dox text.

Comment 7 Aravinda VK 2015-01-20 09:14:57 UTC

Changing priority to Medium since the pause/resume is used only while taking snapshot. After resume, georep worker goes faulty, Monitor restarts the worker and geo-rep will become Stable.