Description of problem: Hybrid crawl restarts from the "start" after geo-replication restarts (due to n/w failure, etc...) Version-Release number of selected component (if applicable): 2.1 How reproducible: Always Steps to Reproduce: 1. create a glusterfs volume, start it and create some data in it (deep directory structure). 2. start geo-replicaition b/w this volume and a slave 3. let some of the directories get synced to the slave 4. take down the n/w b/w master and slave (1 <-> 1 node) 5. bring the n/w up Actual results: the corresponding geo-rep b/w the master and slave node restarts xsync crawl from the start Expected results: The crawl should continue from where it left off. Additional info:
*** This bug has been marked as a duplicate of bug 1031687 ***