Description of problem: CTDB lockvol needs ping-timeout to be changed everytime it is configured make sure this is automated in the post CTDBstart script. Default ping-timeout 42secs for a CTDB lockvol is really high, should be kept at 10secs Version-Release number of selected component (if applicable): mainline How reproducible: Always
REVIEW: http://review.gluster.org/7568 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#1) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/7569 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#1) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/7569 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#2) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/7569 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#3) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/7569 committed in master by Vijay Bellur (vbellur) ------ commit 4044e387dd40e2d12145fd32d5fd715406fcec8e Author: Harshavardhana <harsha> Date: Sat Apr 26 01:29:46 2014 -0700 scripts: CTDB lockvol ping-timeout should be 10secs Users often forget to update the ping-timeout, perhaps we should take care of this automatically Change-Id: I6d14df8aa52665847233cb1760dfd54f41baadec BUG: 1091600 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/7569 Reviewed-by: Raghavendra Talur <rtalur> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Jose A. Rivera <jarrpa> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#1) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#2) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#3) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#4) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#5) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#6) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#7) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/8007 committed in master by Vijay Bellur (vbellur) ------ commit f0c8be68ca68ddb067a40830fecf389c74c13d02 Author: Harshavardhana <harsha> Date: Fri Jun 6 18:43:15 2014 -0700 scripts: CTDB lockvol ping-timeout should be 10secs commit "4044e387dd40e2d12145fd32d5fd715406fcec8e" approach to this led to deadlocks instead we rely on an old trick at client side - without any need to modifying the volume globally. Change-Id: I6e3c6bf9c0a3a0dd99a51b5d2a6c1f050ed2384c BUG: 1091600 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/8007 Reviewed-by: Raghavendra Talur <rtalur> Reviewed-by: Poornima G <pgurusid> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
*** Bug 1105118 has been marked as a duplicate of this bug. ***
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users