-
Notifications
You must be signed in to change notification settings - Fork 543
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: Remove max concurrency reference to query-frontend #3678
Conversation
|
@pstibrany does that mean we can safely conclude that this change makes sense, and I can move the PR out of draft mode? |
I'm pretty sure that's the case, but would like someone to double-check that finding. |
I'll move it out of draft mode then and wait for another review. Thanks! |
bfa6fc6
to
566bb16
Compare
566bb16
to
cf9db11
Compare
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.
I agree it's not used anymore in the query-frontend. LGTM (modulo a couple of nits).
Remove reference to query-frontend for flag -querier.max-concurrent, since it's not used by the query-frontend any longer. Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
Co-authored-by: Marco Pracucci <marco@pracucci.com> Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
d644ce4
to
7f2120c
Compare
…3678) * querier: Remove max concurrency reference to query-frontend Remove reference to query-frontend for flag -querier.max-concurrent, since it's not used by the query-frontend any longer. Also improve the -querier.max-concurrent help text a bit. Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com> Co-authored-by: Marco Pracucci <marco@pracucci.com>
What this PR does
Remove reference to query-frontend for flag -querier.max-concurrent, since it's (probably) not used by the query-frontend any longer.
@pstibrany observed that most likely the
-querier.max-concurrent
flag is not in use by the query-frontend since #2598, but its help string still says it has to be set also for the query-frontend.TODO:
-querier.max-concurrent
is really not in use by the query-frontend any longerWhich issue(s) this PR fixes or relates to
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]