+++ This bug was initially created as a clone of Bug #1499566 +++
Description of problem:
Directory renames are not synced in hybrid crawl
Version-Release number of selected component (if applicable):
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
dir2 would not be synced to slave. dir1 still exists on slave
dir1 should be renamed to dir2 on slave
--- Additional comment from Worker Ant on 2017-10-08 13:20:43 EDT ---
REVIEW: https://review.gluster.org/18448 (geo-rep: Fix rename of directory in hybrid crawl) posted (#1) for review on master by Kotresh HR (firstname.lastname@example.org)
--- Additional comment from Worker Ant on 2017-11-10 00:37:00 EST ---
COMMIT: https://review.gluster.org/18448 committed in master by
------------- geo-rep: Fix rename of directory in hybrid crawl
In hybrid crawl, renames and unlink can't be
synced but directory renames can be detected.
While syncing the directory on slave, if the
gfid already exists, it should be rename.
Hence if directory gfid already exists, rename
Signed-off-by: Kotresh HR <email@example.com>
--- Additional comment from Shyamsundar on 2018-03-15 07:18:57 EDT ---
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-4.0.0, please open a new bug report.
glusterfs-4.0.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.