Description of problem: client log flooding with intentional socket shutdown message when a brick is down [2019-02-22 08:24:42.472457] I [socket.c:811:__socket_shutdown] 0-test-vol-client-0: intentional socket shutdown(5) Version-Release number of selected component (if applicable): glusterfs-6 How reproducible: Always Steps to Reproduce: 1. 1 X 3 volume created and started over a 3 node cluster 2. mount a fuse client 3. kill a brick 4. Observe that fuse client log is flooded with the intentional socket shutdown message after every 3 seconds. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/22396 (transport/socket: move shutdown msg to DEBUG loglevel) posted (#1) for review on release-6 by Raghavendra G
REVIEW: https://review.gluster.org/22482 (logging: Fix GF_LOG_OCCASSIONALLY API) posted (#2) for review on release-6 by Raghavendra G
REVIEW: https://review.gluster.org/22487 (transport/socket: log shutdown msg occasionally) posted (#1) for review on release-6 by Raghavendra G
REVIEW: https://review.gluster.org/22482 (logging: Fix GF_LOG_OCCASSIONALLY API) merged (#3) on release-6 by Shyamsundar Ranganathan
REVIEW: https://review.gluster.org/22487 (transport/socket: log shutdown msg occasionally) merged (#2) on release-6 by Shyamsundar Ranganathan
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.1, please open a new bug report. glusterfs-6.1 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-April/000124.html [2] https://www.gluster.org/pipermail/gluster-users/