Description of problem: When file modifications are happening while index heal is launched, index healer could pick up entries which appeared in indices/xattrop transiently during the course of the operations on the mount point, and do not really need any heal. This will cause index healer to keep doing index-heal in a loop by believing that it did successfully heal some gfids even when it didn't. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/9713 (cluster/afr: Do not increment healed_count if no healing was performed) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9713 (cluster/afr: Do not increment healed_count if no healing was performed) posted (#2) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9713 (cluster/afr: Do not increment healed_count if no healing was performed) posted (#3) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9713 (cluster/afr: Do not increment healed_count if no healing was performed) posted (#4) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9713 (cluster/afr: Do not increment healed_count if no healing was performed) posted (#5) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9713 (cluster/afr: Do not increment healed_count if no healing was performed) posted (#6) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/9713 (cluster/afr: Do not increment healed_count if no healing was performed) posted (#7) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/9713 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 4a8384fe76aeef652554c48df737d3178eb0160c Author: Krutika Dhananjay <kdhananj> Date: Thu Feb 19 19:35:17 2015 +0530 cluster/afr: Do not increment healed_count if no healing was performed PROBLEM: When file modifications are happening while index heal is launched, index healer could pick up entries which appeared in indices/xattrop transiently during the course of the operations on the mount point, and do not really need any heal. This will cause index healer to keep doing index-heal in a loop as long as it finds this entry, by believing that it did successfully heal some gfids even when it didn't. FIX: afr_selfheal() now returns a 1 to indicate that it did not (need to) heal a given gfid. afr_shd_selfheal() will not increment healed_count whenever afr_selfheal() returns a 1. Change-Id: I0d97e11392a032a852e8c6508f691300ef0e5b98 BUG: 1194305 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/9713 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> Reviewed-by: Ravishankar N <ravishankar> Tested-by: Gluster Build System <jenkins.com>
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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user