KAFKA-20292 [2/N]: Handle membership changes during offloaded streams assignments#21727
Open
squah-confluent wants to merge 1 commit intoapache:trunkfrom
Conversation
… assignments When a member leaves a group, its target assignment is directly removed. When a static member is replaced, its target assignment is moved to the new member. These target assignment updates can happen while an offloaded assignment is being computed. When an offloaded assignment has finished, we must not emit records for members that have left the group and we must apply any static member replacements that occurred to the emitted records, to match the behavior when assignments are not offloaded. That is, we act as if the member removals and static member replacements are reordered after the assignment. We break up the assignment process into two parts: computing the target assignment map and generating the records. Only the former can run on the executor. To generate the records without removed members and with static member replacements applied we need to use the current state of the group.
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.
When a member leaves a group, its target assignment is directly removed.
When a static member is replaced, its target assignment is moved to the
new member. These target assignment updates can happen while an
offloaded assignment is being computed.
When an offloaded assignment has finished, we must not emit records for
members that have left the group and we must apply any static member
replacements that occurred to the emitted records, to match the
behavior when assignments are not offloaded. That is, we act as if the
member removals and static member replacements are reordered after the
assignment.
We break up the assignment process into two parts: computing the target
assignment map and generating the records. Only the former can run on
the executor. To generate the records without removed members and with
static member replacements applied we need to use the current state of
the group.