Description of problem: first crawl will be history crawl even though change_detector is xsync. Version-Release number of selected component (if applicable): glusterfs-3.6.0.22-1.el6rhs How reproducible: Happen everytime. Steps to Reproduce: 1. create and start a geo-rep relationship between master and slave. 2. set change_detector to xsync 3. stop geo-rep 4. create data on master, 5. start geo-rep and check the crawl status. Actual results: even though change_detector is xsync, first crawl will be history. Expected results: When change_detector is xsync, it should always use hybrid crawl. Additional info:
Upstream patch sent: http://review.gluster.org/#/c/8183/
Please review and signoff edited doc text.
Doc text looks good to me.
Patch sent to downstream: https://code.engineering.redhat.com/gerrit/#/c/28223/
Verified on the build glusterfs-3.6.0.25-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