+++ This bug was initially created as a clone of Bug #1691616 +++ +++ This bug was initially created as a clone of Bug #1679904 +++ 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: --- Additional comment from Worker Ant on 2019-03-22 05:14:20 UTC --- REVIEW: https://review.gluster.org/22395 (transport/socket: move shutdown msg to DEBUG loglevel) posted (#1) for review on master by Raghavendra G --- Additional comment from Worker Ant on 2019-04-03 04:13:29 UTC --- REVIEW: https://review.gluster.org/22395 (transport/socket: log shutdown msg occasionally) merged (#5) on master by Raghavendra G
This is marked as WONTFIX, as the patches were posted for glusterfs-6 branch, and will also be available on glusterfs-7 releases onwards. Not planning to backport it to release-5 as it doesn't qualify with backporting guideline.