You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Uladzislau Blok (Jira)" <ji...@apache.org> on 2026/09/08 05:36:00 UTC
[jira] [Assigned] (KAFKA-21046) Make Kafka Streams KIP-909 ready
[ https://issues.apache.org/jira/browse/KAFKA-21046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uladzislau Blok reassigned KAFKA-21046:
---------------------------------------
Assignee: Uladzislau Blok
> Make Kafka Streams KIP-909 ready
> --------------------------------
>
> Key: KAFKA-21046
> URL: https://issues.apache.org/jira/browse/KAFKA-21046
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 4.4.0
> Reporter: Matthias J. Sax
> Assignee: Uladzislau Blok
> Priority: Major
>
> KIP-909 ships improved error handling behavior for Kafka clients with regard to DNS changes, and broker re-discovery. However, it also introduces behavior changes and new exceptions when enabled. For this reason, it's locked down in Kafka Streams at the moment and cannot be enable.
> This ticket is about updating KS code base do become KIP-909 ready: we need to change the code to allow to handle the new exceptions correctly, ie, don't let StreamsThread die, but recover fully automatically (what required to create a new client instance).
> We need to also take care of state-updater, global-thread, and the admin client.
> Open question: KIP-909 is disabled on the clients because it requires code changes to handle the new behavior correctly. We could consider to enable it by default in KafkaStreams right away, w/o the need of a major release. If we update KS code to handle it correctly, there should not be any backward compatibility concerns requiring to wait for 5.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)