[
https://issues.apache.org/jira/browse/KAFKA-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-12762.
------------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
> Use connection timeout when polling the network for new connections
> -------------------------------------------------------------------
>
> Key: KAFKA-12762
> URL: https://issues.apache.org/jira/browse/KAFKA-12762
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.7.0, 2.8.0
> Reporter: Mickael Maison
> Assignee: Edoardo Comar
> Priority: Major
> Fix For: 3.1.0
>
>
> In some cases, when connecting to brokers, we end up calling
> selector.select() with the wrong timeout. Since 2.7, we should use a timeout
> computed from socket.connection.setup.timeout.ms to ensure we detect bad
> hosts quickly.
> This is especially relevant now that client.dns.lookup defaults to
> use_all_dns_ips. In case, one of the IPs returned in currently unavailable,
> we want the client to quickly discover it and avoid timing out user calls.
> h4.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
