[
https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164531#comment-17164531
]
Sophie Blee-Goldman commented on KAFKA-10284:
---------------------------------------------
Nope, it just spun in a loop where it would poll and then call
Consumer#position to try and initialize some metadata. Poll just returned empty
I guess and Consumer#position continued to throw TimeoutException.
The TimeoutException part seems pretty weird, so maybe it was an unrelated bug
(or some other issue like a hung socket being the primary/only guess we had). I
just thought of it because it definitely happened immediately after a "id does
not match expected member.id" error.
I actually still have some of the broker and client side logs from around this
incident, if that might help. But again, I'm not really sure if it could be
related to this or not
> 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)
