[ https://issues.apache.org/jira/browse/KAFKA-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059069#comment-17059069 ]
Boyang Chen commented on KAFKA-9568: ------------------------------------ The current design of static membership will not kick-off rebalance as long as we maintain two members with group.instance.id `client-1` and `client-2`. You have to give another instance id like `client-3` to make it actually rebalance. There is another open ticket to add the command line support to force remove a static member from admin client: https://issues.apache.org/jira/browse/KAFKA-9440 That would also help resolve the issue in upcoming 2.6 > Kstreams APPLICATION_SERVER_CONFIG is not updated with static membership > ------------------------------------------------------------------------ > > Key: KAFKA-9568 > URL: https://issues.apache.org/jira/browse/KAFKA-9568 > Project: Kafka > Issue Type: Bug > Components: streams > Affects Versions: 2.4.0 > Reporter: David J. Garcia > Priority: Major > > A kstreams application with static membership, and > StreamsConfg.APPLICATION_SERVER_CONFIG set, will NOT update old server config > upon restart of application on new host. > Steps to reproduce: > > # start two kstreams applications (with same consumer group) and enable > static membership (and set application server config to <ip-addr>:<port>) > # kill one of the applications and restart it on a new host(with new ip) > before timeout ends (so that rebalancing doesn't occur). > # the other kstreams application will now have an invalid > application_server_config > Possible fix: > If an application restarts with a new host/identity..etc, it could trigger a > "light-rebalance" where the other applications in the consumer group don't > change partition assignments ,but instead just get their configuration > updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)