Bug 1091600

Summary:	ctdb start post hook should set ping-timeout to respectable value
Product:	[Community] GlusterFS	Reporter:	Harshavardhana <fharshav>
Component:	scripts	Assignee:	Harshavardhana <fharshav>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, cww, gluster-bugs, rtalur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1092242 (view as bug list)		Environment:
Last Closed:	2014-11-11 08:30:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1092242, 1294224

Description Harshavardhana 2014-04-26 08:28:20 UTC

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

Comment 1 Anand Avati 2014-04-26 08:30:28 UTC

REVIEW: http://review.gluster.org/7568 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#1) for review on master by Harshavardhana (harsha)

Comment 2 Anand Avati 2014-04-26 08:31:12 UTC

REVIEW: http://review.gluster.org/7569 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#1) for review on master by Harshavardhana (harsha)

Comment 3 Anand Avati 2014-04-26 08:33:19 UTC

REVIEW: http://review.gluster.org/7569 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#2) for review on master by Harshavardhana (harsha)

Comment 4 Anand Avati 2014-04-30 05:44:48 UTC

REVIEW: http://review.gluster.org/7569 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#3) for review on master by Harshavardhana (harsha)

Comment 5 Anand Avati 2014-05-02 15:52:52 UTC

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>

Comment 6 Anand Avati 2014-06-07 01:47:47 UTC

REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#1) for review on master by Harshavardhana (harsha)

Comment 7 Anand Avati 2014-06-07 01:50:22 UTC

REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#2) for review on master by Harshavardhana (harsha)

Comment 8 Anand Avati 2014-06-09 19:00:45 UTC

REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#3) for review on master by Harshavardhana (harsha)

Comment 9 Anand Avati 2014-06-09 20:01:15 UTC

REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#4) for review on master by Harshavardhana (harsha)

Comment 10 Anand Avati 2014-06-09 20:06:22 UTC

REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#5) for review on master by Harshavardhana (harsha)

Comment 11 Anand Avati 2014-06-10 07:01:07 UTC

REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#6) for review on master by Harshavardhana (harsha)

Comment 12 Anand Avati 2014-06-11 04:18:44 UTC

REVIEW: http://review.gluster.org/8007 (scripts: CTDB lockvol ping-timeout should be 10secs) posted (#7) for review on master by Harshavardhana (harsha)

Comment 13 Anand Avati 2014-06-12 06:08:44 UTC

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>

Comment 14 Niels de Vos 2014-07-13 11:20:40 UTC

*** Bug 1105118 has been marked as a duplicate of this bug. ***

Comment 15 Niels de Vos 2014-09-22 12:38:58 UTC

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/

Comment 16 Niels de Vos 2014-11-11 08:30:57 UTC

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