Description of problem: statedump from io-threads lacks information to understand the number of running threads & number of requests in each priority queue. Would be good to have this information captured in statedump for observability and debuggability.
REVIEW: https://review.gluster.org/21667 (performance/io-threads: Improve debuggability in statedump) posted (#3) for review on master by Vijay Bellur
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/