Description of problem: geo-rep syncs files through hybrid crawl after history crawl is finished even though changelogs are available for the files changes after history end time. This is particularly a problem, if those changelogs have renames and removals. Version-Release number of selected component (if applicable): glusterfs-3.6.0.20-1.el6rhs How reproducible: Happens everytime. Steps to Reproduce: 1. create and start a geo-rep relationship between master(6x2) and slave (6x2) 2. start creating files using the command "refi -T 10 -n 10 --multi -d 10 -b 10 --random --max=10K --min=1K /mnt/master/ " 3. while this program is running, stop geo-rep for some time and then start geo-rep, such that the above program creates many files after the start of geo-rep. 4. check the log files for xsync-changelog consumption and check the content of the changelogs. Actual results: geo-rep syncs files through hybrid crawl after history crawl is finished even though changelogs are available. Expected results: After history consumption, if there are changelogs, it should start consuming that., Additional info:
Upstream patch sent for review: http://review.gluster.org/#/c/8151/
Please review edited doc text and sign off.
verified on the build glusterfs-3.6.0.27-1
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