Description of problem: while doing first xsync crawl, disconnection with slave causes the geo-rep to re-crawl the whole file system and generate XSYNC-CHANGELOGS again. Version-Release number of selected component (if applicable): glusterfs-3.4.0.44rhs How reproducible:Happens everytime Steps to Reproduce: 1.create a geo-rep relationship between master and slave 2.create some 20million files on master. 3.start a geo-rep session. Actual results: some of the sessions experience disconnections with the slave and first xsync crawl does a full crawl again generated the XSYNC-CHANGELOG with the entries which has already been crawled . Expected results: It shouldn't do this recrawl, it should start from where it has left off Additional info:
*** Bug 1034238 has been marked as a duplicate of this bug. ***
https://code.engineering.redhat.com/gerrit/#/c/17876/ -> U1 https://code.engineering.redhat.com/gerrit/#/c/17877/ -> U2
Added Doc Text
Verified on the build glusterfs-3.4.0.53rhs-1. Steps used to verify. 1.create a geo-rep relationship between master and slave. 2.create 500K files on master. 3.start a geo-rep session between master and slave. 4.run following on one of the master active nodes. while : ; do ps ax | grep "ssh " | awk '{print $1}' | xargs kill ; sleep 100 ; ps ax | grep "ssh " | awk '{print $1}' | xargs kill ; sleep 1000; done 5. Wait for it to complete the syncing.
Can you please verify the doc text for technical accuracy?
Doc text looks fine.
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-0208.html