Bug 1001066

Summary:	Dist-geo-rep : when change-detector is change log, due to some reason if fails to sync any entry from changelog, it keeps retrying and stuck there (no data is synced from that bricks to slave as it keeps retrying)
Product:	Red Hat Gluster Storage	Reporter:	Rachana Patel <racpatel>
Component:	geo-replication	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED ERRATA	QA Contact:	amainkar
Severity:	high	Docs Contact:
Priority:	urgent
Version:	2.1	CC:	aavati, amarts, csaba, rhs-bugs, surs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.24rhs-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-23 22:38:52 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:

Description Rachana Patel 2013-08-26 12:36:52 UTC

Description of problem:
 Dist-geo-rep : when change-detector is change log, due to some reason if fails to sync any entry from changelog, it keeps retrying and stuck there (no data is synced from that bricks to slave as it keeps retrying) 

Version-Release number of selected component (if applicable):
3.4.0.20rhs-2.el6_4.x86_64

How reproducible:
always

Steps to Reproduce:
1.create a geo rep session between master and slave and start it.
2. Inject some fault such that it is unable to create entry on slave(e.g. files from other user than root)
3. It keep processing same change long and keeps re trying. data created after that on that bricks are not synced to slave because of that 

Actual results:


Expected results:


Additional info:

Comment 2 Amar Tumballi 2013-08-27 10:32:33 UTC

https://code.engineering.redhat.com/gerrit/#/c/12027/

This is one patch fixing many similar issues and hence you see just one bug number in commit msg.

Comment 3 Rachana Patel 2013-09-09 13:04:17 UTC

unable to reproduce with 3.4.0.32rhs-1.el6_4.x86_64, hence marking it as verified

Comment 4 Scott Haines 2013-09-23 22:38:52 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html

Comment 5 Scott Haines 2013-09-23 22:41:31 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html