REVIEW: http://review.gluster.org/5319 (cluster/dht: Prevent dht_access from going into a loop.) posted (#1) for review on master by Shishir Gowda (sgowda)
REVIEW: http://review.gluster.org/5319 (cluster/dht: Prevent dht_access from going into a loop.) posted (#2) for review on master by Shishir Gowda (sgowda)
REVIEW: http://review.gluster.org/5319 (cluster/dht: Prevent dht_access from going into a loop.) posted (#3) for review on master by Shishir Gowda (sgowda)
COMMIT: http://review.gluster.org/5319 committed in master by Anand Avati (avati) ------ commit 3e1d8e1689c47d8b83343a403e7d09c018472155 Author: shishir gowda <sgowda> Date: Thu Jul 11 13:44:51 2013 +0530 cluster/dht: Prevent dht_access from going into a loop. If access fails with ENOTCONN, do not wind to same subvol. We wind to first-up-subvol if access fails with ENOTCONN. In few cases, if dht has only 1 subvolume, and access fails with ENOTCONN, we go into a infinite loop of winding to same subvol The fix is to check if we previously wound to same subvol, and fail if first-up-subvol is same. Change-Id: Ib5d3ce7d33e8ea09147905a7df1ed280874fa549 BUG: 983431 Signed-off-by: shishir gowda <sgowda> Reviewed-on: http://review.gluster.org/5319 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
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.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user