Bug 1113525

Summary:	Dist-geo-rep : first crawl will be history crawl even though change_detector is xsync.
Product:	[Community] GlusterFS	Reporter:	Aravinda VK <avishwan>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	aavati, avishwan, bugs, csaba, david.macdonald, gluster-bugs, nlevinki
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1113471	Environment:
Last Closed:	2014-11-11 08:36:00 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:	1113471
Bug Blocks:

Comment 1 Anand Avati 2014-06-26 11:03:26 UTC

REVIEW: http://review.gluster.org/8183 (geo-rep: Change detector method issue) posted (#1) for review on master by Aravinda VK (avishwan)

Comment 2 Anand Avati 2014-06-26 11:04:29 UTC

REVIEW: http://review.gluster.org/8183 (geo-rep: History Change detector method select issue) posted (#2) for review on master by Aravinda VK (avishwan)

Comment 3 Anand Avati 2014-07-01 10:59:09 UTC

COMMIT: http://review.gluster.org/8183 committed in master by Venky Shankar (vshankar) 
------
commit 86ee23319284e62351488f5c76625f0bb3aaad73
Author: Aravinda VK <avishwan>
Date:   Thu Jun 26 16:25:59 2014 +0530

    geo-rep: History Change detector method select issue
    
    Geo-rep does history crawl even if change-detector is set
    to xsync.
    
    This patch fixes by taking priority to user configured
    change detector.
    
    BUG: 1113525
    Change-Id: Ic6c34e187c9cb6608c9ef8a010ea07015ba60a80
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/8183
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kotresh HR <khiremat>
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Venky Shankar <vshankar>

Comment 4 Niels de Vos 2014-09-22 12:43:50 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 5 Niels de Vos 2014-11-11 08:36:00 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users