-
Notifications
You must be signed in to change notification settings - Fork 15.1k
KAFKA-20198: Fix StickyTaskAssignor capacity calculation to use proportional instance limit #22006
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
Open
ChoMinGi
wants to merge
3
commits into
apache:trunk
Choose a base branch
from
ChoMinGi:kafka-20198-sticky-assignor-fix
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+82
−5
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
9514547
KAFKA-20198: Fix StickyTaskAssignor capacity calculation to use propo…
ChoMinGi bd36598
KAFKA-20198: Add regression and convergence tests for proportional in…
ChoMinGi b4f5298
KAFKA-20198: Fix convergence test to use reporter's scenario (450/20)
ChoMinGi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 think this needs a regression test that fails with the old quota math and passes with the new proportional ceiling.
On top of that, can we add a behavior test that simulates repeated StickyTaskAssignor.assign(...) rounds, and then assert that an uneven-capacity case converges in 2 rounds? That would cover the actual failure mode described in the PR, not just the arithmetic change.
Uh oh!
There was an error while loading. Please reload this page.
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.
@harimm
Thanks for the review! Added two tests
shouldRetainFairShareOfPreviousTasksWhenScalingUp— verifies that an instance keeps all 225 of its previous tasks (450 tasks / 2×10 threads). Fails with the old floor-based limit (220).shouldConvergeWithinTwoRoundsWhenScalingUp— simulates repeated assign() rounds with the reporter's scenario and asserts convergence within 2 rounds. Fails with floor due to 10-task overflow bouncing.Let me know if you'd like any adjustments.