REVIEW: http://review.gluster.org/8677 (cluster/dht: Prevent dht_access from going into a loop.) posted (#1) for review on release-3.4 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/8677 (cluster/dht: Prevent dht_access from going into a loop.) posted (#2) for review on release-3.4 by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/8677 (cluster/dht: Prevent dht_access from going into a loop.) posted (#3) for review on release-3.4 by Raghavendra G (rgowdapp)
COMMIT: http://review.gluster.org/8677 committed in release-3.4 by Kaleb KEITHLEY (kkeithle) ------ commit 91175b38c9264676d75a275c16add45f7c64f4c1 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: 1139996 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> Reviewed-on: http://review.gluster.org/8677 Reviewed-by: N Balachandran <nbalacha> Reviewed-by: Kaleb KEITHLEY <kkeithle>