You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Boyang Chen (Jira)" <ji...@apache.org> on 2020/03/14 01:08:00 UTC

[jira] [Assigned] (KAFKA-9568) Kstreams APPLICATION_SERVER_CONFIG is not updated with static membership

     [ https://issues.apache.org/jira/browse/KAFKA-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boyang Chen reassigned KAFKA-9568:
----------------------------------

    Assignee: Sophie Blee-Goldman

> 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
>            Assignee: Sophie Blee-Goldman
>            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)