Bug 1034238

Summary: dist-geo-rep: xsync crawl's resilience to geo-replication restarts.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Venky Shankar <vshankar>
Component: geo-replicationAssignee: Venky Shankar <vshankar>
Status: CLOSED DUPLICATE QA Contact: Vijaykumar Koppad <vkoppad>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: aavati, bbandari, grajaiya, khiremat, nsathyan, vagarwal, vbhat, vkoppad
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-11 08:17:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Venky Shankar 2013-11-25 13:23:40 UTC 
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:
Comment 2 Kotresh HR 2013-12-11 08:17:56 UTC 

*** This bug has been marked as a duplicate of bug 1031687 ***