[
https://issues.apache.org/jira/browse/KAFKA-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039505#comment-17039505
]
Boyang Chen commented on KAFKA-9568:
------------------------------------
Thanks for reporting this, I'm not sure I fully understood the question here.
So let's suppose to have two instances A & B, we first migrate A to another
host so that it's APPLICATION_SERVER_CONFIG would change, while instance B
should still be using the same ip address and port as it is not restarting. So
why would B get an invalid config in this case?
> 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.3.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)
