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
Describe the bug
We have found that when using the setting match_max_concurrent our queriers are only processing 1 query in parallel instead of the expected queriers max_concurrent setting. This can be seen by looking at the loki_inflight_requests metric on the queriers which should show a busy querier dong max_concurrent inflight requests.
As a workaround, in the worker config section you can remove the match_max_concurrent setting and instead set parallelism equal to max_concurrent
This was introduced in #4301, first affected released would be 2.4
The text was updated successfully, but these errors were encountered:
Describe the bug
We have found that when using the setting
match_max_concurrent
our queriers are only processing 1 query in parallel instead of the expected queriersmax_concurrent
setting. This can be seen by looking at theloki_inflight_requests
metric on the queriers which should show a busy querier dongmax_concurrent
inflight requests.As a workaround, in the
worker
config section you can remove thematch_max_concurrent
setting and instead setparallelism
equal tomax_concurrent
This was introduced in #4301, first affected released would be 2.4
The text was updated successfully, but these errors were encountered: