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
We try to cancel long expensive query by having lower than default timeout(2m). We are setting it to 1m (reference) but we are seeing long term expensive historical queries taking 100s which is causing resource starvation issues and impact other queries.
How to reproduce it?
Start Mimir 2.14.3
Set querier.timeout to 1m under querier block (ref), execute some expensive query which takes more than a minute and it's not timing out.
What did you think would happen?
Expected behavior: Query should timeout after a min if timeout is being set to 1m.
Actual behavior: Expensive query are taking > 100s to execute causing SGW resource starvation and impacting other smaller query.
What was your environment?
Kubernetes
Any additional context to share?
No response
The text was updated successfully, but these errors were encountered:
What is the bug?
Hello team,
We try to cancel long expensive query by having lower than default timeout(2m). We are setting it to 1m (reference) but we are seeing long term expensive historical queries taking 100s which is causing resource starvation issues and impact other queries.
How to reproduce it?
What did you think would happen?
Expected behavior: Query should timeout after a min if timeout is being set to 1m.
Actual behavior: Expensive query are taking > 100s to execute causing SGW resource starvation and impacting other smaller query.
What was your environment?
Kubernetes
Any additional context to share?
No response
The text was updated successfully, but these errors were encountered: