+++ This bug was initially created as a clone of Bug #1753857 +++
+++ This bug was initially created as a clone of Bug #1726000 +++
Description of problem:
The bz#1694820
addresses issue for RENAME issue when handling RENAME with existing destination. This fix requires some performance tuning considering this issue occurs in heavy rename workload.
Version-Release number of selected component (if applicable):
master
How reproducible:
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:
Expected results:
Additional info:
--- Additional comment from Worker Ant on 2019-09-20 05:30:34 UTC ---
REVIEW: https://review.gluster.org/23459 (geo-rep: performance improvement while syncing renames with existing gfid) posted (#1) for review on master by Sunny Kumar
--- Additional comment from Worker Ant on 2019-09-23 12:07:40 UTC ---
REVIEW: https://review.gluster.org/23459 (geo-rep: performance improvement while syncing renames with existing gfid) merged (#2) on master by Kotresh HR
REVIEW: https://review.gluster.org/23475 (geo-rep: performance improvement while syncing renames with existing gfid) posted (#1) for review on release-7 by Kotresh HR
REVIEW: https://review.gluster.org/23475 (geo-rep: performance improvement while syncing renames with existing gfid) merged (#1) on release-7 by Kotresh HR