+++ This bug was initially created as a clone of Bug #1664235 +++ Description of problem: ======================= Directory renames are not synced to the slave in Hybrid crawl. Version-Release number of selected component (if applicable): ============================================================= mainline How reproducible: ================= Always Steps to Reproduce: =================== 1. Setup geo-replication 2. Set the change_detector to xsync 3. Create directory (dir1) on master and let it sync to slave 4. rename dir1 to dir2 Actual results: =============== Dir1 still exists in the slave instead of Dir2 Expected results: ================= Dir2 should be seen on the slave as well. Additional info: ================ There were no errors seen in geo-rep logs regarding the failure to rename the directory.
REVIEW: https://review.gluster.org/22020 (geo-rep : fix rename sync on hybrid crawl) posted (#1) for review on master by Sunny Kumar
REVIEW: https://review.gluster.org/22020 (geo-rep : fix rename sync on hybrid crawl) merged (#4) on master by Kotresh HR
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/