Bug 1105466

Summary:	Dist-geo-rep : geo-rep history crawl consumes even zero-byte changelogs and accumulates in .history/.processed directory of working_dir
Product:	[Community] GlusterFS	Reporter:	Ajeet Jha <ajha>
Component:	geo-replication	Assignee:	Ajeet Jha <ajha>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	mainline	CC:	aavati, avishwan, bugs, csaba, david.macdonald, gluster-bugs, nlevinki, nsathyan, ssamanta
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:	1104153	Environment:
Last Closed:	2014-11-11 08:34:35 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:	1104153
Bug Blocks:

Comment 1 Anand Avati 2014-06-06 08:38:10 UTC

REVIEW: http://review.gluster.org/7949 (features/changelog: skipping empty changelogs in history) posted (#3) for review on master by ajeet jha (ajha)

Comment 2 Anand Avati 2014-06-10 13:38:10 UTC

COMMIT: http://review.gluster.org/7949 committed in master by Venky Shankar (vshankar) 
------
commit 94260c93a144b52964a27ddc9eaef869a3e8f354
Author: Ajeet Jha <ajha>
Date:   Mon Jun 2 14:49:07 2014 +0530

    features/changelog: skipping empty changelogs in history
    
    Empty changelgs are unlinked and htime-update is bypassed
    while publishing partially written changelog.
    
    Change-Id: I1533ad431e4fbf592d2f38837fce782932d01e9c
    BUG: 1105466
    Signed-off-by: Ajeet Jha <ajha>
    Reviewed-on: http://review.gluster.org/7949
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Venky Shankar <vshankar>

Comment 3 Niels de Vos 2014-09-22 12:42:22 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 4 Niels de Vos 2014-11-11 08:34:35 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