Description of problem: geo-rep history crawl consumes even zero-byte changelog and accumulates in .history/.processed directory of working_dir. snippet of the output. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> # ls */.history/.processed -lrt -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792481 -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792541 -rw-r--r-- 1 root root 4182 Jun 3 16:21 CHANGELOG.1401792556 -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792616 -rw-r--r-- 1 root root 29406 Jun 3 16:21 CHANGELOG.1401792571 -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792601 -rw-r--r-- 1 root root 4940 Jun 3 16:21 CHANGELOG.1401792586 -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792676 -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792661 -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792646 -rw-r--r-- 1 root root 0 Jun 3 16:21 CHANGELOG.1401792631 # ls */.history/.processed -lrt | wc -l 887 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This is bad, since we unnecessarily consume inodes from root partition or wherever this working_dir is mounted. Version-Release number of selected component (if applicable): glusterfs-3.6.0.10-1.el6rhs How reproducible: Happens every time. Steps to Reproduce: 1. create and start a geo-rep relationship between master and slave 2. stop the geo-rep 3. wait for some time 4. create some data on master. 5. start geo-rep Actual results: History crawl consumes zero-byte changelogs Expected results: History crawl should ignore zero byte changelogs. Additional info:
Upstream patch is available for review. http://review.gluster.org/#/c/7949/
After discussing with the Engineering-Leads at RHS3.0 status meeting providing the qa_ack for the same.
http://review.gluster.org/#/c/7949/
Downstream Patch : https://code.engineering.redhat.com/gerrit/#/c/26666/
Verified on the build glusterfs-3.6.0.24-1.el6rhs
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1278.html