[
https://issues.apache.org/jira/browse/KAFKA-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039685#comment-17039685
]
David J. Garcia commented on KAFKA-9568:
----------------------------------------
B would have an incorrect A mapping. For example, suppose that there was a
state-store with some data on A and other data on B. Here is some scala that
I'm using:
{code:java}
val keyHostInfo: Option[IQHost] = Option(streamsRef.metadataForKey(
storeName,
docId,
Implicits.keySerde.serializer)).map(m => IQHost(m.host(), m.port(),
thisHost.IQConfig))
//m is of type StreamsMetadata
{code}
StreamsMetadata has mappings that link the partition of docId to a host/port.
Sometimes the host is the current machine, other times its on another machine
(as reported by that machine to the controller)
> 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)
