-
Notifications
You must be signed in to change notification settings - Fork 14k
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
KAFKA-13406: skip assignment validation for built-in cooperativeStickyAssignor #11439
Conversation
@showuon something like this would be a good fix for 3.1, especially since it's quick and code freeze is coming up. I also feel it is low-risk, for one thing this validation clearly can't be trusted at the moment anyways, for another I think it's fair to trust the CooperativeStickyAssignor since we have many tests for it -- we could just move the validation check from the ConsumerCoordinator into the CooperativeStickyAssignor itself, but we essentially already do exactly that inside the |
Oh, I didn't notice the v3.1.0 is going to code freeze soon. I thought I can still wait for the Andrei's test. Thanks for reminding, @ableegoldman . I'll clean it up today. |
Well, "soon" -- I just saw the notice about feature freeze coming up, so it's not a rush exactly, but just wanted to give a heads up in case if you're like me and didn't see the 3.1 deadlines coming up because 3.0 seemed like it was only a few weeks ago 😅 |
@ableegoldman , it's good to review now. Thanks. |
@ableegoldman , please take a look when available. Thank you. |
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.
LGTM, sorry for the delayed review
Failure is unrelated, merging to trunk. Will also need to cherrypick back to 3.1 cc @dajac |
…yAssignor (#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
…yAssignor (#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
Merged to trunk and ported back to 3.0 and 2.8, just waiting for David's approval before cherrypicking to the 3.1 branch |
@ableegoldman Approved. |
…yAssignor (#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
Thanks! Pushed to 3.1 as well |
…yAssignor (apache#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
…yAssignor (#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
…yAssignor (#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
…yAssignor (#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
…yAssignor (apache#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
…yAssignor (apache#11439) This fix is trying to skip the assignment validation for built-in cooperative sticky assignor, since (a) we know the assignment is valid since we do essentially this same check already in the cooperative sticky assignor, and (b) the check is broken anyways due to potential for claimed `ownedPartitions` to be incorrect Reviewers: Anna Sophie Blee-Goldman <ableegoldman@apache.org>
This fix is trying to skip the assignment validation for built-in cooperative sticky assignor. And also add tests.
Committer Checklist (excluded from commit message)