Bug 1111577

Summary: Dist-geo-rep : geo-rep syncs files through hybrid crawl after history crawl is finished even though changelogs are available.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vijaykumar Koppad <vkoppad>
Component: geo-replicationAssignee: Aravinda VK <avishwan>
Status: CLOSED ERRATA QA Contact: Bhaskar Bandari <bbandari>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.0CC: aavati, avishwan, bbandari, csaba, david.macdonald, khiremat, nlevinki, nsathyan, sharne, ssamanta
Target Milestone: ---   
Target Release: RHGS 3.0.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.6.0.27-1 Doc Type: Known Issue
Doc Text:
Geo-replication synchronizes files through hybrid crawl after it completes full file system crawl and does not utilize changelogs during that time. Due to this, deletes and renames happened during that window is not propagated to slave. Hence, Slave will have additional files compared to Master.
Story Points: ---
Clone Of:
: 1112238 (view as bug list) Environment:
Last Closed: 2014-09-22 19:42:29 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:
Bug Depends On:    
Bug Blocks: 1087818, 1109557, 1112238, 1122502    

Description Vijaykumar Koppad 2014-06-20 12:11:21 UTC
Description of problem: geo-rep syncs files through hybrid crawl after history crawl is finished even though changelogs are available for the files changes after history end time.  This is particularly a problem, if those changelogs  have renames and removals. 


Version-Release number of selected component (if applicable): glusterfs-3.6.0.20-1.el6rhs


How reproducible: Happens everytime.


Steps to Reproduce:
1. create and start a geo-rep relationship between master(6x2) and slave (6x2)
2. start creating files using the command "refi -T 10 -n 10 --multi -d 10 -b 10 --random --max=10K --min=1K /mnt/master/ "
3. while this program is running, stop geo-rep for some time and then start geo-rep, such that the above program creates many files after the start of geo-rep. 
4. check the log files for xsync-changelog consumption and check the content of the changelogs. 

Actual results: geo-rep syncs files through hybrid crawl after history crawl is finished even though changelogs are available.


Expected results: After history consumption, if there are changelogs, it should start consuming that., 



Additional info:

Comment 2 Aravinda VK 2014-06-23 11:54:04 UTC
Upstream patch sent for review: http://review.gluster.org/#/c/8151/

Comment 3 Shalaka 2014-07-01 10:52:38 UTC
Please review edited doc text and sign off.

Comment 5 Vijaykumar Koppad 2014-08-05 09:30:35 UTC
verified on the build glusterfs-3.6.0.27-1

Comment 9 errata-xmlrpc 2014-09-22 19:42:29 UTC
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