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/22474 (geo-rep: fix rename with existing gfid) posted (#1) for review on master by Sunny Kumar
REVIEW: https://review.gluster.org/22519 (geo-rep: Fix rename with existing destination with same gfid) posted (#1) for review on master by Kotresh HR
REVIEW: https://review.gluster.org/22519 (geo-rep: Fix rename with existing destination with same gfid) merged (#7) on master by Amar Tumballi