Bug 1319710 - glusterd: disable ping timer b/w glusterd and make epoll thread count default 1
Summary: glusterd: disable ping timer b/w glusterd and make epoll thread count default 1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHGS 3.1.3
Assignee: Atin Mukherjee
QA Contact: SATHEESARAN
URL:
Whiteboard: glusterd
Depends On:
Blocks: 1311817
TreeView+ depends on / blocked
 
Reported: 2016-03-21 11:20 UTC by Atin Mukherjee
Modified: 2016-09-17 16:45 UTC (History)
11 users (show)

Fixed In Version: glusterfs-3.7.9-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1271750
Environment:
Last Closed: 2016-06-23 05:05:11 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1240 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 Update 3 2016-06-23 08:51:28 UTC

Comment 3 Atin Mukherjee 2016-03-21 11:22:22 UTC 
This bug is to track the fix which was already in 3.1.2 but missed out as part of rebasing to 3.1.3 from upstream 3.7.9
Comment 4 Atin Mukherjee 2016-03-21 13:22:26 UTC 
Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/70340/
Comment 6 SATHEESARAN 2016-03-29 07:53:11 UTC 
Verified with RHGS 3.1.3 nightly build ( glusterfs-3.7.9-1.el7rhgs )

1. glusterd ping-timer is disabled
2. There is only one glusterd epoll thread

Here is the snip of glusterd volfile

<snip>
[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     <---- ping-timer disabled
    option event-threads 1    <---- only one glusterd epoll thread
#   option base-port 49152
end-volume
</snip>
Comment 8 errata-xmlrpc 2016-06-23 05:05:11 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://access.redhat.com/errata/RHBA-2016:1240
Note You need to log in before you can comment on or make changes to this bug.