Bug 1364421

Summary:	[RFE] History Crawl performance improvement
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Aravinda VK <avishwan>
Component:	geo-replication	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	low	Docs Contact:
Priority:	low
Version:	rhgs-3.1	CC:	atumball, bugs, csaba, rhinduja, rhs-bugs, srangana
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-18	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1364420
Clones:	1365119 (view as bug list)		Environment:
Last Closed:	2018-10-11 10:32:23 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:	1364420, 1374153, 1503170
Bug Blocks:	1365119

Description Aravinda VK 2016-08-05 10:17:46 UTC

+++ This bug was initially created as a clone of Bug #1364420 +++

Description of problem:
If History changelogs backlog to be processed is more then Geo-rep takes lot of time to reach to current state because of rsync retries.

Issue and possible solution is discussed in upstream
http://www.gluster.org/pipermail/gluster-devel/2016-August/050372.html

Comment 6 Amar Tumballi 2018-10-11 10:32:23 UTC

We have the fix in codebase as part of the rebases done for 3.4.0 release.