[ 
https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Boyang Chen updated KAFKA-10284:
--------------------------------
    Description: 
For known static members rejoin, we would update its corresponding member.id 
without triggering a new rebalance. This serves the purpose for avoiding 
unnecessary rebalance for static membership, as well as fencing purpose if some 
still uses the old member.id. 

The bug is that we don't actually persist the membership update, so if no 
upcoming rebalance gets triggered, this new member.id information will get lost 
during group coordinator immigration, thus bringing up the zombie member 
identity.

The bug find credit goes to [~hachikuji] 

  was:
For known static members rejoin, we would update its corresponding member.id 
without triggering a new rebalance. This serves the purpose for avoiding 
unnecessary rebalance for static membership, as well as fencing purpose if some 
still uses the old member.id. 

The bug is that we don't actually persist the membership update, so if no 
upcoming rebalance gets triggered, this new member.id information will get lost 
during group coordinator immigration, thus bringing up the zombie member 
identity.


> Group membership update due to static member rejoin should be persisted
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-10284
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10284
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.6.0
>            Reporter: Boyang Chen
>            Assignee: Boyang Chen
>            Priority: Major
>             Fix For: 2.6.1
>
>
> For known static members rejoin, we would update its corresponding member.id 
> without triggering a new rebalance. This serves the purpose for avoiding 
> unnecessary rebalance for static membership, as well as fencing purpose if 
> some still uses the old member.id. 
> The bug is that we don't actually persist the membership update, so if no 
> upcoming rebalance gets triggered, this new member.id information will get 
> lost during group coordinator immigration, thus bringing up the zombie member 
> identity.
> The bug find credit goes to [~hachikuji] 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to