Bug #45554
closedmgr/prometheus: cache ineffective when gathering data takes longer than 5 seconds
0%
Description
The cache is considered stale and will not be used if the request takes longer than 5 seconds. This interval can be configured, though.
This is seemingly not a problem for small clusters, but becomes a problem when the request takes longer than 5 seconds and may even become a bigger problem when the gathering of the data takes longer than 10 seconds, as Prometheus requests metrics every 10 seconds (cephadm default configuration). That may lead to requests to the Ceph cluster that will never stop and keep it busy. The data returned will not even be used but Prometheus will (cephadm default configuration) let it time out.
It'd surely make sense to increase the scrape interval in such scenarios, though, the effectively disabled cache will cause even more issues if the metrics are requests in addition to the recurring requests of Prometheus.
Updated by Patrick Seidensal almost 4 years ago
- Status changed from New to In Progress
- Assignee set to Patrick Seidensal
Updated by Patrick Seidensal almost 4 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 35572
Updated by Kefu Chai almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46171: octopus: mgr/prometheus: cache ineffective when gathering data takes longer than 5 seconds added
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46172: nautilus: mgr/prometheus: cache ineffective when gathering data takes longer than 5 seconds added
Updated by Patrick Seidensal almost 4 years ago
- Backport changed from octopus,nautilus to octopus,nautilus,luminous
Updated by Laura Paduano almost 4 years ago
- Copied to Backport #46544: luminous: mgr/prometheus: cache ineffective when gathering data takes longer than 5 seconds added
Updated by Patrick Seidensal almost 4 years ago
- Backport changed from octopus,nautilus,luminous to octopus,nautilus
Updated by Nathan Cutler almost 4 years ago
- Backport changed from octopus,nautilus to octopus,nautilus,luminous
Updated by Nathan Cutler almost 4 years ago
@Patrick, when a backport issue enters Rejected state, we should not remove it from the Backports list, otherwise the "backport-create-issue" script complains:
ERROR:root:https://tracker.ceph.com/issues/45554 has more backport issues (luminous,nautilus,octopus) than expected (nautilus,octopus)
Updated by Nathan Cutler almost 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".