Description of problem: logs are being flooded with logs about ENODATA for same socket Expected results: At most only a single log message with ENODATA for an fd should be logged Additional info:
REVIEW: https://review.gluster.org/21659 (rpc: stop log flooding about ENODATA) posted (#1) for review on master by Milind Changire
Reproducer: 1. Create 10 1 X 3 replica 3 volumes with brick multiplexing enabled. 2. In one of the node kill -9 <brick process id> 3. Tail glusterd log which will flood (never ending) with the socket failures ENODATA logs
REVIEW: https://review.gluster.org/21659 (rpc: stop log flooding about ENODATA) posted (#3) 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/