Description of problem: geo-rep resume after 120 sec of pause, would restart geo-rep instead of resuming.
Version-Release number of selected component (if applicable): glusterfs-188.8.131.52-1.el6rhs
How reproducible: Happens everytime.
Steps to Reproduce:
1. create and start a geo-rep relationship between master and slave.
2. start creating data on master.
3. Pause the geo-rep for more than 120 sec and resume it.
4. Check the status of the geo-rep
Actual results: geo-rep goes to faulty for some time.
Expected results: when resumed, it should actually resume syncing, not restarting the geo-rep.
As agreed by Dev leads, QE and PM, moving the BZ to future release. The issue is not severe as sync of files resumes from the last checkpoint and it does not crawl the entire file system.
Please review and signoff edited dox text.
Changing priority to Medium since the pause/resume is used only while taking snapshot. After resume, georep worker goes faulty, Monitor restarts the worker and geo-rep will become Stable.