-
Notifications
You must be signed in to change notification settings - Fork 524
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
Querier: Refine error messages for per-tenant query limits #5059
Conversation
c831ede
to
73fbc91
Compare
73fbc91
to
716a111
Compare
The CHANGELOG has just been cut to prepare for the next Mimir release. Please rebase |
716a111
to
e78f14c
Compare
@pracucci @charleskorn WDYT of my last revision? Query shards no longer mentioned. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, modulo failing test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM to me too, thanks
f10a577
to
bb77409
Compare
Refine error messages for per-tenant query limits, informing the user of the preferred strategy for not hitting the limit, in addition to how they may tweak the limit. Affected limits: * max_fetched_chunks_per_query * max_fetched_chunk_bytes_per_query * max_fetched_series_per_query Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
Co-authored-by: Charles Korn <charleskorn@users.noreply.github.com>
Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
305168f
to
d46ba11
Compare
What this PR does
Refine error messages for per-tenant query limits, informing the user of the preferred strategy for not hitting the limit, in addition to how they may tweak the limit. It's preferred to not increase these limits if possible, since they're designed to prevent Mimir instability. Affected limits:
I've taken inspiration from the runbooks for the limits in question on the strategy (same for all three) for not hitting them.
Which issue(s) this PR fixes or relates to
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]