You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2021/02/04 11:44:00 UTC
[jira] [Resolved] (KAFKA-12193) Re-resolve IPs when a client is
disconnected
[ https://issues.apache.org/jira/browse/KAFKA-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mickael Maison resolved KAFKA-12193.
------------------------------------
Fix Version/s: 2.8.0
Resolution: Fixed
> Re-resolve IPs when a client is disconnected
> --------------------------------------------
>
> Key: KAFKA-12193
> URL: https://issues.apache.org/jira/browse/KAFKA-12193
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 2.7.0
> Reporter: Bob Barrett
> Assignee: Bob Barrett
> Priority: Major
> Fix For: 2.8.0
>
>
> If `client.dns.lookup` is set to `use_all_dns_ips` or `resolve_canonical_bootstrap_servers_only`, the NetworkClient can store multiple IPs for each node, and currently it tries each IP in the list when connecting before re-resolving the IPs. This is useful when first establishing a connection because it ensures that the client exhausts all possible IPs. However, in the case where the IPs changed after a connection was already established, this would cause a reconnecting client to try several invalid IPs before re-resolving and trying a valid one. Instead, we should re-resolve DNS when a client disconnects from an established connection, rather than assuming the all previously-resolved IPs are still valid.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)