[jira] [Commented] (KAFKA-13467) Clients never refresh cached bootstrap IPs

["Matthew de Detrich (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572788#comment-17572788 ] 

Matthew de Detrich commented on KAFKA-13467:
--------------------------------------------

I am currently having a look at this issue although due to the nature of the ticket I am diving a bit in the deep end. [~rsivaram] , [~ijuma] [~mimaison] would be able to give my some pointers on how to best approach this. Following what [~dengziming] said earlier, I am currently looking at SocketServer which seems to be core of where all of the netty connections are initialized but this may the wrong place to do the change.

Furthermore I may be missing something but if one naively implements the "broker disconnecting a connection when the client connects to force an IP change" would create an infinite loop unless one one checks for a condition (i.e. only on broker upgrade, is this possible) or maybe some other condition?

> Clients never refresh cached bootstrap IPs
> ------------------------------------------
>
>                 Key: KAFKA-13467
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13467
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, network
>            Reporter: Matthias J. Sax
>            Priority: Minor
>
> Follow up ticket to https://issues.apache.org/jira/browse/KAFKA-13405.
> For certain broker rolling upgrade scenarios, it would be beneficial to expired cached bootstrap server IP addresses and re-resolve those IPs to allow clients to re-connect to the cluster without the need to restart the client.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)