Bug 1722598

Summary:	dump the min and max latency of each xlator in statedump
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-26 03:42:24 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 Raghavendra Bhat 2019-06-20 17:40:53 UTC

Description of problem:

When latency monitoring is enabled at per xlator level for a gluster process (via the signal SIGUSR2), taking the statedump wont dump the minimum and maximum latencies seen for each xlator (for each fop).

Dumping that information helps in debugging performance and latency related issues as the statedump helps in identifying the xlator where the latency is seen.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-06-20 17:42:24 UTC

REVIEW: https://review.gluster.org/22910 (statedump: dump the minimum and maximum latency seen by each xlator) posted (#1) for review on master by Raghavendra Bhat

Comment 2 Worker Ant 2019-06-26 03:42:24 UTC

REVIEW: https://review.gluster.org/22910 (statedump: dump the minimum and maximum latency seen by each xlator) merged (#3) on master by Amar Tumballi