[
https://issues.apache.org/jira/browse/KAFKA-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273328#comment-17273328
]
Boyang Chen commented on KAFKA-12169:
-------------------------------------
In general, the leader should be able to detect metadata discrepancy between
its remembered topic metadata and broker side metadata. I don't think we have
any test case to cover both the topic partition change and leader rejoin at the
same time, so it's possible and needs some verification.
> Consumer can not know paritions chage when client leader restart with static
> membership protocol
> ------------------------------------------------------------------------------------------------
>
> Key: KAFKA-12169
> URL: https://issues.apache.org/jira/browse/KAFKA-12169
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 2.5.1, 2.6.1
> Reporter: zou shengfu
> Priority: Major
>
> Background:
> Kafka consumer services run with static membership and cooperative rebalance
> protocol on kubernetes, and services often restart because of operation. When
> we added partitions from 1000 to 2000 for the topic, client leader restart
> with unknown member id at the same time, we found the consumers do not
> tigger rebalance and still consume 1000 paritions
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
