Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1112520

Summary:	Use History API when available instead of switching back to xsync
Product:	[Community] GlusterFS	Reporter:	Aravinda VK <avishwan>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	gluster-bugs
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-02 11:45:11 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 Aravinda VK 2014-06-24 06:46:01 UTC

Description of problem:
When changelogs are available, do not switch to xsync crawl. With xsync crawl both renames and deletes are not propagated.

Actual results(Crawl cycle when worker restarts):
Existing geo-rep uses History -> XSync -> Changelog

Expected results(Crawl cycle when worker restarts):
History -> History -> Changelog

Comment 1 Anand Avati 2014-06-24 07:04:54 UTC

REVIEW: http://review.gluster.org/8157 (geo-rep: minimize xsync crawl usage) posted (#1) for review on master by Aravinda VK (avishwan)

Comment 2 Aravinda VK 2014-07-02 11:45:11 UTC


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