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

Loki: Set querier worker max concurrent regardless of run configuration. #4761

Merged
merged 2 commits into from
Nov 16, 2021

Conversation

slim-bean
Copy link
Collaborator

What this PR does / why we need it:

Be sure to set MaxConcurrentRequests when initializing the querier.

Which issue(s) this PR fixes:
Fixes #4760

Special notes for your reviewer:

Checklist

  • Documentation added
  • Tests updated
  • Add an entry in the CHANGELOG.md about the changes.

@slim-bean slim-bean requested a review from a team as a code owner November 15, 2021 23:59
@slim-bean slim-bean merged commit 88ef940 into main Nov 16, 2021
@slim-bean slim-bean deleted the max-concurent branch November 16, 2021 00:52
trevorwhitney pushed a commit to trevorwhitney/loki that referenced this pull request Jan 27, 2022
…on. (grafana#4761)

* always set the querier worker MaxConcurrentRequests

* removing a test which doesn't apply as this setting isn't being set in worker_service.go anymore

(cherry picked from commit 88ef940)
cyriltovena pushed a commit that referenced this pull request Feb 1, 2022
…nfigurati… (#5256)

* Loki: Set querier worker max concurrent regardless of run configuration. (#4761)

* always set the querier worker MaxConcurrentRequests

* removing a test which doesn't apply as this setting isn't being set in worker_service.go anymore

(cherry picked from commit 88ef940)

* update vendor

* update vendor again, but better?

Co-authored-by: Ed Welch <edward.welch@grafana.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Querier worker not using correct parallelism when using match_max_concurrent
2 participants