REVIEW: http://review.gluster.org/13186 (geo-rep: avoid creating multiple entries with same gfid) posted (#2) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/13186 (geo-rep: avoid creating multiple entries with same gfid) posted (#3) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/13186 (geo-rep: avoid creating multiple entries with same gfid) posted (#4) for review on master by Milind Changire (mchangir)
Public comments: The issue manifest when nightly logs are rolled over by customer application using log4j. Investigation revealed that there is an issue with CREATE + RENAME log replay from geo-rep. Patch http://review.gluster.org/13186 is available to resolve the issue.
REVIEW: http://review.gluster.org/13316 (georep: avoid creating multiple entries with same gfid) posted (#1) for review on master by Milind Changire (mchangir)
COMMIT: http://review.gluster.org/13316 committed in master by Jeff Darcy (jdarcy) ------ commit 87d93fac9fcc4b258b7eb432ac4151cdd043534f Author: Milind Changire <mchangir> Date: Fri Jan 29 13:53:07 2016 +0530 georep: avoid creating multiple entries with same gfid Problem: CREATE + RENAME changelogs replayed by geo-replication cause stale old-name entries with same gfid on slave nodes. A gfid is a unique key in the file-system and should not be assigned to multiple entries. Solution: Create entry on slave only if lstat(gfid) at aux-mount fails. This applies to files as well as directories. Change-Id: Ice3340f4ae1251c2dcef024a2388c4d33b5d4919 BUG: 1296206 Signed-off-by: Milind Changire <mchangir> Reviewed-on: http://review.gluster.org/13316 Smoke: Gluster Build System <jenkins.com> Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Aravinda VK <avishwan> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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-3.8.0, please open a new bug report. glusterfs-3.8.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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user