[
https://issues.apache.org/jira/browse/KAFKA-20747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-20747:
------------------------------------
Description:
Client generate a random MemberId on startup. Even if low probability, it's
possible that a re-starting client generate the exact same MemberId. For this
case the following happens:
# A group has a static member with member id $memberId and instance id
$instanceId1.
# The member heartbeats with epoch 0, member id $memberId and instance id
$instanceId2.
# The group's `staticMembers` map now contains entries for both $instanceId1
and $instanceId2 both pointing to $memberId.
was:
# A group has a static member with member id $memberId and instance id
$instanceId1.
# The member heartbeats with epoch 0, member id $memberId and instance id
$instanceId2.
# The group's `staticMembers` map now contains entries for both $instanceId1
and $instanceId2 both pointing to $memberId.
> Static member rejoining with same member id and different instance id not
> tracked correctly
> -------------------------------------------------------------------------------------------
>
> Key: KAFKA-20747
> URL: https://issues.apache.org/jira/browse/KAFKA-20747
> Project: Kafka
> Issue Type: Bug
> Components: group-coordinator
> Affects Versions: 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.3.0, 4.0.2, 4.1.1, 4.1.2,
> 4.2.1, 4.3.1
> Reporter: Sean Quah
> Assignee: Sean Quah
> Priority: Minor
>
> Client generate a random MemberId on startup. Even if low probability, it's
> possible that a re-starting client generate the exact same MemberId. For this
> case the following happens:
> # A group has a static member with member id $memberId and instance id
> $instanceId1.
> # The member heartbeats with epoch 0, member id $memberId and instance id
> $instanceId2.
> # The group's `staticMembers` map now contains entries for both $instanceId1
> and $instanceId2 both pointing to $memberId.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
