Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1250810

Summary: Make ping-timeout option configurable at a volume-level
Product: [Community] GlusterFS Reporter: krishnan parthasarathi <kparthas>
Component: rpcAssignee: krishnan parthasarathi <kparthas>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: bkunal, bugs, gluster-bugs, nsathyan, rgowdapp, sasundar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1249499 Environment:
Last Closed: 2015-09-09 09:39:07 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: 1249499    
Bug Blocks: 983307, 1248533, 1252359    

Description krishnan parthasarathi 2015-08-06 04:38:00 UTC 
+++ This bug was initially created as a clone of Bug #1249499 +++

Description of problem:
A gluster volume can have ping-timeout values different from the default 42 secs. This can be done by setting network.ping-timeout option on the volume.

e.g,
# gluster volume set <VOLNAME> network.ping-timeout <preferred-value>

Currently, volume-set doesn't update the ping-timeout on running mounts.


Version-Release number of selected component (if applicable):


How reproducible:
always


Steps to Reproduce:
1. Mount a gluster volume with default ping-timeout value.
2. Change the ping-timeout to a different value with the volume-set command mentioned above.
3. Simulate a network disconnection using iptables(8) or attach gdb to one of the brick processes.

Actual results:
The ping-timeout isn't updated on running mount processes.

Expected results:
The ping-timeout should take effect on running mount processes.


Additional info:

--- Additional comment from Anand Avati on 2015-08-03 04:06:46 EDT ---

REVIEW: http://review.gluster.org/11818 (client, rpc: make ping-timeout configurable for glusterfs clients) posted (#1) for review on master by Krishnan Parthasarathi (kparthas)

--- Additional comment from Anand Avati on 2015-08-05 03:25:02 EDT ---

COMMIT: http://review.gluster.org/11818 committed in master by Raghavendra G (rgowdapp) 
------
commit 3403370ebeaf16567b79022c6ac48b2e0cd50db5
Author: Krishnan Parthasarathi <kparthas>
Date:   Mon Aug 3 13:28:09 2015 +0530

    client, rpc: make ping-timeout configurable for glusterfs clients
    
    Change-Id: Idd94adb0457aaffce7330f56f98cebafa2c4dae8
    BUG: 1249499
    Signed-off-by: Krishnan Parthasarathi <kparthas>
    Reviewed-on: http://review.gluster.org/11818
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: NetBSD Build System <jenkins.org>
Comment 1 Kaushal 2015-09-09 09:39:07 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.7.4, please open a new bug report.

glusterfs-3.7.4 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/12496
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user