You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Boyang Chen (Jira)" <ji...@apache.org> on 2020/08/12 22:49:00 UTC

[jira] [Comment Edited] (KAFKA-10284) Group membership update due to static member rejoin should be persisted

    [ https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176639#comment-17176639 ] 

Boyang Chen edited comment on KAFKA-10284 at 8/12/20, 10:48 PM:
----------------------------------------------------------------

I would say for all. Let me check if [~feyman] is interested in picking this up.


was (Author: bchen225242):
I would say for all.

> 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
>            Priority: Major
>              Labels: help-wanted
>
> 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)