[ https://issues.apache.org/jira/browse/KAFKA-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203622#comment-17203622 ]
Guozhang Wang commented on KAFKA-10513: --------------------------------------- [~mou@ea] could you try setting the `metadata.max.age.ms` to a very small value and retry this scenario again? [~bchen225242] and I looked at both client and broker side code in 2.6 and we think it should still trigger rebalance. > Newly added topic or partitions are not assigned to running consumer groups > using static membership > --------------------------------------------------------------------------------------------------- > > Key: KAFKA-10513 > URL: https://issues.apache.org/jira/browse/KAFKA-10513 > Project: Kafka > Issue Type: Bug > Components: consumer > Affects Versions: 2.6.0 > Reporter: Marlon Ou > Priority: Major > > If consumers are polling messages from a certain topic with static membership > and we add new partitions to this topic while the consumers are running, no > partition reassignment is ever triggered (and hence messages published into > the new partitions are never consumed). > To reproduce, simply set group instance IDs on the consumers: > {code:java} > props.setProperty("group.instance.id", instanceId); > {code} > And then while the static consumers are running, use Kafka's admin client to > add more partitions to the topic: > {code:java} > adminClient.createPartitions(...) > {code} > -- This message was sent by Atlassian Jira (v8.3.4#803005)