Bug 1722598 - dump the min and max latency of each xlator in statedump
Summary: dump the min and max latency of each xlator in statedump
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-20 17:40 UTC by Raghavendra Bhat
Modified: 2019-06-26 03:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-26 03:42:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Gluster.org Gerrit 22910 None Merged statedump: dump the minimum and maximum latency seen by each xlator 2019-06-26 03:42:23 UTC

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


Note You need to log in before you can comment on or make changes to this bug.