Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1664124

Summary:	Improve information dumped from io-threads in statedump
Product:	[Community] GlusterFS	Reporter:	Vijay Bellur <vbellur>
Component:	io-threads	Assignee:	Vijay Bellur <vbellur>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-25 16:33:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vijay Bellur 2019-01-07 19:15:34 UTC

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.

Comment 1 Worker Ant 2019-01-07 19:35:10 UTC

REVIEW: https://review.gluster.org/21667 (performance/io-threads: Improve debuggability in statedump) posted (#3) for review on master by Vijay Bellur

Comment 2 Worker Ant 2019-01-08 05:20:36 UTC

REVIEW: https://review.gluster.org/21667 (performance/io-threads: Improve debuggability in statedump) posted (#3) for review on master by Vijay Bellur

Comment 3 Shyamsundar 2019-03-25 16:33:00 UTC

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/