[
https://issues.apache.org/jira/browse/KAFKA-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059093#comment-17059093
]
Sophie Blee-Goldman commented on KAFKA-9568:
--------------------------------------------
In KIP-568/KAFKA-9525 we added a new #enforceRebalance API to the consumer, in
part to address the fact that we can't otherwise force static members to
rebalance. This was a problem for version probing and the upcoming KIP-441,
which rely on triggering rebalances for each member to send their new/updated
metadata. This seems like a similar situation, so I think we can leverage
#enforceRebalance here as well by having a "new" member check the host info in
its returned assignment and trigger the group to rebalance if it doesn't match
the current expected host info.
Of course this doesn't help existing apps, anything older than 2.6 would still
require manual intervention as Boyang described
> 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)
