[
https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163796#comment-17163796
]
Sophie Blee-Goldman commented on KAFKA-10284:
---------------------------------------------
You know, I think we actually hit this too, but weren't able to recognize the
problem at the time. A few weeks ago one of our StreamThreads/Consumers seemed
to "take off" from the group at some point, as evidenced by the steadily
increasing last-rebalance-seconds-ago metric (whereas the other members had
rebalanced multiple times since then). Right before this occurred we saw that
same error message in the logs:
{code:java}
ERROR given member.id X is identified as a known static member 1,but not
matching the expected member.id Y (kafka.coordinator.group.GroupMetadata)
{code}
Unfortunately we killed the client trying to remotely debug it so we couldn't
get any more useful information. Would you say that this was mysterious
encounter was likely due to the bug reported here? [~guozhang] [~bchen225242]
> 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)
