Bug 1102524 – Dist-geo-rep : geo-rep resume after 120 sec of pause, would make geo-rep faulty and restarts instead of resuming.

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1102524 - Dist-geo-rep : geo-rep resume after 120 sec of pause, would make geo-rep faulty and restarts instead of resuming.

Summary:	Dist-geo-rep : geo-rep resume after 120 sec of pause, would make geo-rep faul...

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	geo-replication (Show other bugs)
Sub Component:
Version:	3.0
Hardware:	x86_64 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Bug Updates Notification Mailing List
QA Contact:	storage-qa-internal@redhat.com
Docs Contact:

URL:
Whiteboard:	usability
Keywords:	ZStream

Depends On:
Blocks:	1087818
	Show dependency tree / graph

Reported:	2014-05-29 02:43 EDT by Vijaykumar Koppad
Modified:	2018-04-16 11:58 EDT (History)
CC List:	9 users (show)

See Also:
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 11:58:16 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Vijaykumar Koppad 2014-05-29 02:43:17 EDT

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 03:22:49 EDT

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 07:11:49 EDT

Please review and signoff edited dox text.

Comment 7 Aravinda VK 2015-01-20 04:14:57 EST

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.

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