Bug 1066410

Summary:	xsync creates 0byte files and skips replication
Product:	[Community] GlusterFS	Reporter:	Aravinda VK <avishwan>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	pre-release	CC:	aavati, bugs, csaba, david.macdonald, fdacunha, fharshav, gluster-bugs, kcleveng, nlevinki, nsathyan, vshankar
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:	1064597	Environment:
Last Closed:	2014-11-11 08:28:02 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:	1064597
Bug Blocks:

Comment 2 Anand Avati 2014-02-19 05:16:03 UTC

REVIEW: http://review.gluster.org/7021 (geo-rep: Do not create empty Xsync changelog files) posted (#2) for review on master by Aravinda VK (avishwan)

Comment 3 Anand Avati 2014-06-09 08:20:38 UTC

REVIEW: http://review.gluster.org/8003 (geo-rep: Making replica failover check interval configurable) posted (#2) for review on master by Aravinda VK (avishwan)

Comment 4 Anand Avati 2014-06-12 06:55:39 UTC

COMMIT: http://review.gluster.org/8003 committed in master by Venky Shankar (vshankar) 
------
commit ee1ef00e2aee6f25b75d156c24ce7f5aab4529a4
Author: Aravinda VK <avishwan>
Date:   Fri Jun 6 16:04:40 2014 +0530

    geo-rep: Making replica failover check interval configurable
    
    Replica failover check interval is hardcoded to 60 sec
    by default. Now this option is made configurable and
    defaulted to 1 sec.
    
    To change the default value
    gluster volume geo-replication <MASTERVOL> \
    	<SLAVEHOST>::<SLAVEVOL> config replica_failover_interval 15
    
    Change-Id: Iada1b80d510452dcfedebd8a21bebd62394b0597
    BUG: 1066410
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/8003
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: Venky Shankar <vshankar>

Comment 5 Niels de Vos 2014-09-22 12:36:09 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 6 Niels de Vos 2014-11-11 08:28:02 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