Rationale: Heavy IO keeps the single event-thread busy with reading messages from the network and queuing them to the request handler threads. Messages remain unread at the socket while the request is being queued to the request handler threads. Time is thus wasted while messages accumulate in the socket buffers. To achieve better responsiveness and thus avoid ping-timer expiry, it has been observed that multiple event-threads help in achieving the same. Additional event-threads help in improving system performance as well since they help in reading requests sooner and get them serviced sooner than they would with the single event-thread model. Therefore the need to bump up the default value of event-threads to a better value.
REVIEW: https://review.gluster.org/21719 (rpc: bump up server.event-threads) posted (#2) for review on master by Milind Changire
REVIEW: https://review.gluster.org/21719 (rpc: bump up server.event-threads) posted (#4) for review on master by Raghavendra G
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-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/