Red Hat Bugzilla – Bug 1250810
Make ping-timeout option configurable at a volume-level
Last modified: 2015-11-03 18:06:36 EST
+++ 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.
# 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):
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.
The ping-timeout isn't updated on running mount processes.
The ping-timeout should take effect on running mount processes.
--- 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 (email@example.com)
--- 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 (firstname.lastname@example.org)
Author: Krishnan Parthasarathi <email@example.com>
Date: Mon Aug 3 13:28:09 2015 +0530
client, rpc: make ping-timeout configurable for glusterfs clients
Signed-off-by: Krishnan Parthasarathi <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Raghavendra G <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.