Red Hat Bugzilla – Bug 984591
Dist-geo-rep : renames to files will be synced as a new files without actually renaming on slave side by first xsync crawl.
Last modified: 2015-11-25 03:51:54 EST
Description of problem: If files which were synced to slave are renamed after stopping the geo-rep session, and geo-rep starts , the first xsync crawl will sync those renamed files as new files to slave without actually renaming the slaves. If 100 files were renamed , you would get 200 files on the slave side.
Version-Release number of selected component (if applicable):184.108.40.206rhs.beta4-1.el6rhs.x86_64
How reproducible: Consitently
Steps to Reproduce:
1.Create and start a geo-rep relationship between master(DIST-REP) and slave.
2.Create files using the command, ./crefi.py -n 10 --multi -b 10 -d 10 --random --max=500K --min=10 <MNT_PNT>
3.Let it sync to slave.
4. Stop the geo-rep session,
5. rename all the files, using the command ./crefi.py -n 10 --multi -b 10 -d 10 --random --max=500K --min=10 --fop=rename <MNT_PNT>
6. start the geo-rep session.
7. Check the number of files on master and slave.
Actual results: renames to files will be synced as a new files without actually renaming on slave side by first xsync crawl.
Expected results: if renames are done on master, it should be renames on the slaves too.
the first sync is intended to get the data on master to slave and anything after that is captured in 'changelog' and then only we are able to capture all the fops. Currently expected behavior, and behavior was same with earlier implementation.
Closing this bug since RHGS 2.1 release reached EOL. Required bugs are cloned to RHGS 3.1. Please re-open this issue if found again.