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

Query-scheduler performance issue after #5880 #6090

Closed
pracucci opened this issue Sep 21, 2023 · 2 comments · Fixed by #6100
Closed

Query-scheduler performance issue after #5880 #6090

pracucci opened this issue Sep 21, 2023 · 2 comments · Fixed by #6100
Assignees

Comments

@pracucci
Copy link
Collaborator

We're analyzing some read path latency which recently got worse and we've found that looks like there's an issue with the query-scheduler after #5880, which causes the time it takes to enqueue a query in the query-scheduler to grow over time. Looking when the issue started, it began with the rollout of the weekly release n. 255.

The average enqueue latency is measured using:

sum by(namespace) (rate(cortex_query_scheduler_enqueue_duration_seconds_sum{container="query-scheduler"}[5m]))
/
sum by(namespace) (rate(cortex_query_scheduler_enqueue_duration_seconds_count{container="query-scheduler"}[5m]))
* 1000

We can observe that it grows over time. For example, this is our staging environment:

Screenshot 2023-09-21 at 12 50 52

These are a couple of our production environments:

Screenshot 2023-09-21 at 12 53 12

@pracucci
Copy link
Collaborator Author

In our staging environment, it looks like the issue didn't show after upgrading from weekly release 255 to 256. The weekly release 256 was rolled out on 2023-09-20 at 16:30 UTC:

Screenshot 2023-09-21 at 13 29 00

@charleskorn
Copy link
Contributor

I believe #6100 will fix this issue. See the description in the PR for more details.

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

Successfully merging a pull request may close this issue.

2 participants