Bug 1112520 - Use History API when available instead of switching back to xsync
Summary: Use History API when available instead of switching back to xsync
Keywords:
Status: CLOSED DUPLICATE of bug 1112238
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-24 06:46 UTC by Aravinda VK
Modified: 2014-07-02 11:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-02 11:45:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Aravinda VK 2014-06-24 06:46:01 UTC
Description of problem:
When changelogs are available, do not switch to xsync crawl. With xsync crawl both renames and deletes are not propagated.

Actual results(Crawl cycle when worker restarts):
Existing geo-rep uses History -> XSync -> Changelog

Expected results(Crawl cycle when worker restarts):
History -> History -> Changelog

Comment 1 Anand Avati 2014-06-24 07:04:54 UTC
REVIEW: http://review.gluster.org/8157 (geo-rep: minimize xsync crawl usage) posted (#1) for review on master by Aravinda VK (avishwan)

Comment 2 Aravinda VK 2014-07-02 11:45:11 UTC

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


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