This bug was initially created as a copy of Bug #1694820 I am copying this bug because: Description of problem: This problem only exists in heavy RENAME workload where parallel rename are frequent or doing RENAME with existing destination. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run frequent RENAME on master mount and check for sync in slave. Ex - while true; do uuid="`uuidgen`"; echo "some data" > "test$uuid"; mv "test$uuid" "test" -f; done Actual results: Does not syncs renames properly and creates multiples files in slave. Expected results: Should sync renames.
REVIEW: https://review.gluster.org/22723 (geo-rep: Fix rename with existing destination with same gfid) posted (#1) for review on release-6 by Kotresh HR
REVIEW: https://review.gluster.org/22723 (geo-rep: Fix rename with existing destination with same gfid) merged (#2) on release-6 by Amar Tumballi