frankvicky opened a new pull request, #23364: URL: https://github.com/apache/kafka/pull/23364
KIP-909's asynchronous bootstrap DNS resolution mode (enabled by a positive `bootstrap.resolve.timeout.ms`) surfaces failures as `BootstrapResolutionException` from regular API calls on a permanently broken client that must be discarded and rebuilt by the caller. Neither Kafka Streams nor Kafka Connect is prepared to handle that recovery contract for the clients they create internally, so a user enabling the config would break both frameworks (see KAFKA-20939). Since the config is marked as an evolving/experimental feature (KAFKA-20969), disable it in both frameworks for the time being: - Streams: StreamsConfig forces the config to 0 for the main, restore and global consumers, the producer, and the admin client, logging a warning when a user-supplied value is overridden. - Connect: client config maps built by Worker (connector/task producers, consumers, admin clients, including per-connector overrides) and by the config/offset/status backing stores force the config to 0 via a new ConnectUtils helper; DistributedConfig forces the parsed value to 0 so the herder's own network client also stays in synchronous mode. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
