[
https://issues.apache.org/jira/browse/KAFKA-10284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163248#comment-17163248
]
Akshay Sharma edited comment on KAFKA-10284 at 7/23/20, 6:24 AM:
-----------------------------------------------------------------
Hi [~bchen225242]/[~guozhang],
I've raised the bug related to the same issue 6 days ago. Please look at it
once.
https://issues.apache.org/jira/browse/KAFKA-10285
Analysis,
`when i've not restarted the broker and restarted consumer, I could see below
logs`
```
[2020-07-16 13:56:17,189] INFO [GroupCoordinator 1001]: Preparing to rebalance
group 0 in state PreparingRebalance with old generation 0
(__consumer_offsets-48) (reason: Adding new member 1-1594907777144 with group
instanceid Some(1)) (kafka.coordinator.group.GroupCoordinator)
[2020-07-16 13:56:17,236] INFO [GroupCoordinator 1001]: Stabilized group 0
generation 1 (__consumer_offsets-48) (kafka.coordinator.group.GroupCoordinator)
[2020-07-16 13:56:17,282] INFO [GroupCoordinator 1001]: Assignment received
from leader for group 0 for generation 1
(kafka.coordinator.group.GroupCoordinator)
********
[2020-07-16 13:59:33,613] INFO [GroupCoordinator 1001]: Static member Some(1)
with unknown member id rejoins, assigning new member id 1-1594907777335, while
old member 1-1594907777144 will be removed.
(kafka.coordinator.group.GroupCoordinator)
[2020-07-16 13:59:33,635] INFO [GroupCoordinator 1001]: Static member joins
during Stable stage will not trigger rebalance.
(kafka.coordinator.group.GroupCoordinator)
```
when restarted the broker, I could see broker is expecting some other
member.id(old member.id of consumer)
```
2020-07-16 14:04:04,953] ERROR given member.id 1-1594907777335 is identified
as a known static member 1,but not matching the expected member.id
1-1594907777144 (kafka.coordinator.group.GroupMetadata)
```
was (Author: akshaysh):
Hi [~bchen225242]/[~guozhang],
I've raised the bug related to the same issue. Please look at it once.
https://issues.apache.org/jira/browse/KAFKA-10285
Analysis,
`when i've not restarted the broker and restarted consumer, I could see below
logs`
```
[2020-07-16 13:56:17,189] INFO [GroupCoordinator 1001]: Preparing to rebalance
group 0 in state PreparingRebalance with old generation 0
(__consumer_offsets-48) (reason: Adding new member 1-1594907777144 with group
instanceid Some(1)) (kafka.coordinator.group.GroupCoordinator)
[2020-07-16 13:56:17,236] INFO [GroupCoordinator 1001]: Stabilized group 0
generation 1 (__consumer_offsets-48) (kafka.coordinator.group.GroupCoordinator)
[2020-07-16 13:56:17,282] INFO [GroupCoordinator 1001]: Assignment received
from leader for group 0 for generation 1
(kafka.coordinator.group.GroupCoordinator)
********
[2020-07-16 13:59:33,613] INFO [GroupCoordinator 1001]: Static member Some(1)
with unknown member id rejoins, assigning new member id 1-1594907777335, while
old member 1-1594907777144 will be removed.
(kafka.coordinator.group.GroupCoordinator)
[2020-07-16 13:59:33,635] INFO [GroupCoordinator 1001]: Static member joins
during Stable stage will not trigger rebalance.
(kafka.coordinator.group.GroupCoordinator)
```
when restarted the broker, I could see broker is expecting some other
member.id(old member.id of consumer)
```
2020-07-16 14:04:04,953] ERROR given member.id 1-1594907777335 is identified as
a known static member 1,but not matching the expected member.id 1-1594907777144
(kafka.coordinator.group.GroupMetadata)
```
> 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)
