[Bugs] [Bug 1210627] New: ping-timeout value available in glusterd statedump is incorrect
bugzilla at redhat.com
bugzilla at redhat.com
Fri Apr 10 08:46:44 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1210627
Bug ID: 1210627
Summary: ping-timeout value available in glusterd statedump is
incorrect
Product: GlusterFS
Version: 3.7.0
Component: glusterd
Severity: medium
Assignee: bugs at gluster.org
Reporter: sasundar at redhat.com
QA Contact: sasundar at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Description of problem:
-----------------------
glusterd statedump has a incorrect value for ping-timeout
Version-Release number of selected component (if applicable):
--------------------------------------------------------------
glusterfs-3.7 nightly builds ( glusterfs-3.7dev-0.952.gita7f1d08.el6.x86_64
)
How reproducible:
-----------------
Always
Steps to Reproduce:
--------------------
1. Take a statedump of glusterd
(i.e) kill -USR1 `pidof glusterd`
2. check for the ping-timeout value available in glusterd statedump
(i.e) grep ping-timeout /var/run/gluster/glusterdump*
Actual results:
---------------
Ping timeout has a value 0 in glusterd statedump
Expected results:
-----------------
Ping timeout value available in glusterd statedump should be 30
Additional info:
-----------------
[root@ ~]# grep ping-timeout /var/run/gluster/glusterdump*
glusterd.ping-timeout=0
[root@ ~]# grep ping-timeout /etc/glusterfs/glusterd.vol
option ping-timeout 30
[root@ ~]# grep ping-timeout /var/log/glusterfs/etc-glusterfs-glusterd.vol.log
8: option ping-timeout 30
7: option ping-timeout 30
7: option ping-timeout 30
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list