Conversation
Sarama can now take part in incremental cooperative rebalances as described in KIP-429. Instead of stopping every partition claim when membership changes, it stops only the claims the broker has revoked and continues consuming from the rest while it rejoins the group. The consumer group session stays alive throughout that process. Offset commits and partition watches remain tied to the active generation. KIP-429: https://cwiki.apache.org/confluence/display/KAFKA/KIP-429%3A%2BKafka%2BConsumer%2BIncremental%2BRebalance%2BProtocol Signed-off-by: Dominic Evans <dominic.evans@uk.ibm.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Sarama can now take part in incremental cooperative rebalances as described in KIP-429. Instead of stopping every partition claim when membership changes, it stops only the claims the broker has revoked and continues consuming from the rest while it rejoins the group.
The consumer group session stays alive throughout that process. Offset commits and partition watches remain tied to the active generation.
KIP-429: https://cwiki.apache.org/confluence/display/KAFKA/KIP-429%3A%2BKafka%2BConsumer%2BIncremental%2BRebalance%2BProtocol
Fixes #1858