Bug 1230186 - disable ping timer between glusterds
Summary: disable ping timer between glusterds
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: All
OS: All
high
urgent
Target Milestone: ---
: RHGS 3.1.0
Assignee: Atin Mukherjee
QA Contact: SATHEESARAN
URL:
Whiteboard: glusterd
Depends On:
Blocks: 1202842
TreeView+ depends on / blocked
 
Reported: 2015-06-10 12:16 UTC by Atin Mukherjee
Modified: 2015-07-29 05:01 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.7.1-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RHEL 6.7 RHEL 7.1
Last Closed: 2015-07-29 05:01:03 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 0 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 08:26:26 UTC

Description Atin Mukherjee 2015-06-10 12:16:04 UTC
Description of problem:

glusterd.vol has ping timer set to 30 by default which means ping timer will be enabled by default. The expectation is to disable ping timer.

Comment 2 Atin Mukherjee 2015-06-10 12:20:16 UTC
This is a downstream requirement, so no upstream patch is required. Downstream patch link : https://code.engineering.redhat.com/gerrit/50430

Comment 6 SATHEESARAN 2015-06-12 17:05:47 UTC
Tested with RHGS 3.1 Nightly Build ( glusterfs-3.7.1-2.el6rhs ) and observed that the ping-timer is disabled.

<snip_glusterd_volfile>
[root@ ~]# cat /etc/glusterfs/glusterd.vol 
volume management
    type mgmt/glusterd
    option working-directory /var/lib/glusterd
    option transport-type socket,rdma
    option transport.socket.keepalive-time 10
    option transport.socket.keepalive-interval 2
    option transport.socket.read-fail-log off
    option ping-timeout 0
#   option base-port 49152
end-volume
</snip_glusterd_volfile>

Marking this bug as VERIFIED

Comment 7 errata-xmlrpc 2015-07-29 05:01:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1495.html


Note You need to log in before you can comment on or make changes to this bug.