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

[v23.1.x] kafka: Disable use of separate fetch scheduling group #12035

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #11919
Fixes: #12034,

This partially reverts 9a93a9c

While the original motiviation isn't invalidated we have now found a
counter example where the extra fetch groups makes things worse overall.

`ManyPartitionTest` fails on ARM with the extra group but passes
without. With the group in use CPU util hits 100% and grinds everything
to halt.

Fetch seems to be a lot slower on ARM. Hence, with the guaranteed share
of the extra group the whole system gets affected and hits CPU limits.

Because this is incredibly hard to reason about and it wasn't the core
fetch optimization we decided to revert back to keeping it disabled by
default.

We still keep the option around as it might be useful potentially in
corner cases.

Fixes redpanda-data#10507

(cherry picked from commit 6d1223d)
@vbotbuildovich vbotbuildovich added this to the v23.1.x-next milestone Jul 11, 2023
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Jul 11, 2023
@vbotbuildovich vbotbuildovich requested a review from ballard26 July 11, 2023 18:44
@StephanDollberg StephanDollberg marked this pull request as ready for review July 12, 2023 09:41
@StephanDollberg StephanDollberg merged commit 1c2fc17 into redpanda-data:v23.1.x Jul 12, 2023
@BenPope BenPope modified the milestones: v23.1.x-next, v23.1.14 Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants