| Summary: | glusterd: disable ping timer b/w glusterd and make epoll thread count default 1 | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Atin Mukherjee <amukherj> |
| Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.1 | CC: | bsrirama, nlevinki, rcyriac, rhinduja, rhs-bugs, sankarshan, sasundar, smohan, storage-qa-internal, vagarwal, vbellur |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.1.3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | glusterd | ||
| Fixed In Version: | glusterfs-3.7.9-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1271750 | Environment: | |
| Last Closed: | 2016-06-23 05:05:11 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1311817 | ||
|
Comment 3
Atin Mukherjee
2016-03-21 11:22:22 UTC
Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/70340/ 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>
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 |