You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2018. It is now read-only.
The flush handlers for metrics with higher resolutions should be given higher priority compared to those with lower resolutions to ensure alerts and dashboards are still working in cases where the agg servers are temporarily overloaded. This could be done by assigning different priorities to items queued on the bucket heap where buckets with high resolutions have higher priorities and are at the top of the heap and as such will be flushed earlier than those with lower resolutions.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
cc @martin-mao
The flush handlers for metrics with higher resolutions should be given higher priority compared to those with lower resolutions to ensure alerts and dashboards are still working in cases where the agg servers are temporarily overloaded. This could be done by assigning different priorities to items queued on the bucket heap where buckets with high resolutions have higher priorities and are at the top of the heap and as such will be flushed earlier than those with lower resolutions.
The text was updated successfully, but these errors were encountered: