Description of problem:
Changelogs are not capturing renames and hence dependant applications like geo-rep and glusterfind are failing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set distributed gluster volume
2. Enable changelog
3. Mount the volume and do rename of a file
4. Check the backend changelog for the rename record.
Rename is not getting recorded by changelog
Rename should be recorded by changelog.
The changelog would journal the rename of files only when the DHT sends a special key on the hashed subvol. The key is not being set.
root@fedora4#gluster vol info
Volume Name: master
Volume ID: a2eacd30-cd0a-4d20-867e-8c9f465341bd
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
This is happening only one single dht subvolume. There is a new change in DHT which just does default rename if there is single subvol and this missed the changelog key to be set in xdata.
REVIEW: https://review.gluster.org/20093 (cluster/dht: Fix rename journal in changelog) posted (#1) for review on master by Kotresh HR
COMMIT: https://review.gluster.org/20093 committed in master by "Kotresh HR" <email@example.com> with a commit message- cluster/dht: Fix rename journal in changelog
With patch , renames are journalled only
on cached subvolume. The dht sends the special
key on the cached subvolume so that the changelog
journals the rename. With single distribute
sub-volume, the key is not being set. This patch
fixes the same.
Signed-off-by: Kotresh HR <firstname.lastname@example.org>
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-5.0, please open a new bug report.
glusterfs-5.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.