[
https://issues.apache.org/jira/browse/KAFKA-12169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286251#comment-17286251
]
zou shengfu commented on KAFKA-12169:
-------------------------------------
"restart with unknown member id", this mean restart the client leader, because
my service run on k8s, and container is scheduled at any time. When I add
partitions and the container is scheduled and restarted.
Broker version is 2.3.0 and I merge some commit about rebalance after version
2.3.0
> Consumer can not know paritions change 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)
