-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Do Not Update Partition Pausing Field In CMLC #2350
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
Comments
garyrussell
added a commit
to garyrussell/spring-kafka
that referenced
this issue
Jul 13, 2022
Resolves spring-projects#2350 Do not maintain the `pausePartitionsRequested` field in the concurrent MLC, it is not used and can cause confusion. Also resolves spring-projects#2222 The previous fix removed revoked partitions from `pausePartitionsRequested`; this was incorrect - consider a rebalance where we lose `topic-0` and another rebalance where we are re-assigned `topic-0`. According to the contract, this partition should remain paused. **cherry-pick to 2.9.x, 2.8.x**
garyrussell
added a commit
to garyrussell/spring-kafka
that referenced
this issue
Jul 13, 2022
Resolves spring-projects#2350 Do not maintain the `pausePartitionsRequested` field in the concurrent MLC, it is not used and can cause confusion. Also resolves spring-projects#2222 The previous fix removed revoked partitions from `pausePartitionsRequested`; this was incorrect - consider a rebalance where we lose `topic-0` and another rebalance where we are re-assigned `topic-0`. According to the contract, this partition should remain paused. **cherry-pick to 2.9.x, 2.8.x**
garyrussell
added a commit
to garyrussell/spring-kafka
that referenced
this issue
Jul 13, 2022
Resolves spring-projects#2350 Do not maintain the `pausePartitionsRequested` field in the concurrent MLC, it is not used and can cause confusion. Also fixes some synchronization around `CMLC.containers`. Also resolves spring-projects#2222 The previous fix removed revoked partitions from `pausePartitionsRequested`; this was incorrect - consider a rebalance where we lose `topic-0` and another rebalance where we are re-assigned `topic-0`. According to the contract, this partition should remain paused. **cherry-pick to 2.9.x, 2.8.x**
artembilan
pushed a commit
that referenced
this issue
Jul 13, 2022
Resolves #2350 Do not maintain the `pausePartitionsRequested` field in the concurrent MLC, it is not used and can cause confusion. Also fixes some synchronization around `CMLC.containers`. Also resolves #2222 The previous fix removed revoked partitions from `pausePartitionsRequested`; this was incorrect - consider a rebalance where we lose `topic-0` and another rebalance where we are re-assigned `topic-0`. According to the contract, this partition should remain paused. **cherry-pick to 2.9.x, 2.8.x**
artembilan
pushed a commit
that referenced
this issue
Jul 13, 2022
Resolves #2350 Do not maintain the `pausePartitionsRequested` field in the concurrent MLC, it is not used and can cause confusion. Also fixes some synchronization around `CMLC.containers`. Also resolves #2222 The previous fix removed revoked partitions from `pausePartitionsRequested`; this was incorrect - consider a rebalance where we lose `topic-0` and another rebalance where we are re-assigned `topic-0`. According to the contract, this partition should remain paused. **cherry-pick to 2.9.x, 2.8.x**
artembilan
pushed a commit
that referenced
this issue
Jul 13, 2022
Resolves #2350 Do not maintain the `pausePartitionsRequested` field in the concurrent MLC, it is not used and can cause confusion. Also fixes some synchronization around `CMLC.containers`. Also resolves #2222 The previous fix removed revoked partitions from `pausePartitionsRequested`; this was incorrect - consider a rebalance where we lose `topic-0` and another rebalance where we are re-assigned `topic-0`. According to the contract, this partition should remain paused. **cherry-pick to 2.9.x, 2.8.x**
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#2222 (comment)
Fields for paused partitions are only used in the KMLC but they also exist in the CMLC and can get out of whack after a rebalance, causing confusion.
Remove the fields from the AMLC.
The text was updated successfully, but these errors were encountered: