[
https://issues.apache.org/jira/browse/KAFKA-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736981#comment-16736981
]
Andrey Dyachkov commented on KAFKA-7621:
----------------------------------------
Hi, [~batzee]
Any updated on this?
I am seeing similar behaviour 2.1.0, after restarting one Kafka broker and its
ip is changed, the consumer is trying to connect to the ip address which is not
there anymore, forever.
{code:java}
[Consumer clientId=consumer-18297, groupId=] Connection to node 67108872
(/172.31.160.25:9092) could not be established. Broker may not be
available.{code}
> Clients can't deal with server IP address change
> ------------------------------------------------
>
> Key: KAFKA-7621
> URL: https://issues.apache.org/jira/browse/KAFKA-7621
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 2.0.0
> Reporter: Bastian Voigt
> Priority: Major
>
> When the server IP address changes (and the corresponding DNS record changes,
> of course), the client cannot deal with this. It keeps saying:
> {{Connection to node 0 could not be established. Broker may not be available}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
