Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qos latency seeing spike #2544

Closed
summertony15 opened this issue Dec 11, 2023 · 2 comments · Fixed by #2548
Closed

Qos latency seeing spike #2544

summertony15 opened this issue Dec 11, 2023 · 2 comments · Fixed by #2548
Labels

Comments

@summertony15
Copy link

A note for the community

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please let us know in a comment

Problem

When using "qos_latency" metric in harvest, there is a peak latency from 0 to over 3s showing in the dashboard, and the spike last for around three minutes.
截圖 2023-12-11 16 03 34
This spike happens around three times a day.
From the AIQUM, we didn't see this peak value in the performance dashboard.
And we opened a case, and from the PA dashboard, there didn't have a spike value either,
wondering could be the bug for the harvest metric.

Another cluster that is using an older version of harvest is using metric "qos_volume_latency", and also ran into the same issue, with the peak latency to over 3000s.
截圖 2023-12-11 16 25 47
This spike also lasts for around three minutes.

Another example here is the volume "VM_ISCSI_DS1" latency dashboard in AIQUM and harvest for 24 hours,
In AIQUM:
截圖 2023-12-11 16 28 10
In Harvest with "qos_latency" metric:
截圖 2023-12-11 16 30 41

Configuration

No response

Poller

cluster1

Version

23.11.0

Poller logs

No response

OS and platform

CentOS7.9.2009

ONTAP or StorageGRID version

9.11.1

Additional Context

No response

References

No response

@summertony15
Copy link
Author

open a new ticket related to qos_latency spike value #2597

@rahulguptajss rahulguptajss removed their assignment Feb 12, 2024
@rahulguptajss
Copy link
Contributor

verified in main and long running setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants