Bug 1034238 - dist-geo-rep: xsync crawl's resilience to geo-replication restarts.
Summary: dist-geo-rep: xsync crawl's resilience to geo-replication restarts.
Keywords:
Status: CLOSED DUPLICATE of bug 1031687
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: 2.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 2.1.2
Assignee: Venky Shankar
QA Contact: Vijaykumar Koppad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 13:23 UTC by Venky Shankar
Modified: 2015-05-13 16:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-11 08:17:56 UTC
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.