You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Justinwins (Jira)" <ji...@apache.org> on 2022/07/12 09:16:00 UTC

[jira] [Created] (KAFKA-14068) add node advertised listeners when AdminClient can not connect to the node

Justinwins created KAFKA-14068:
----------------------------------

             Summary: add node advertised listeners  when AdminClient can not connect to the node
                 Key: KAFKA-14068
                 URL: https://issues.apache.org/jira/browse/KAFKA-14068
             Project: Kafka
          Issue Type: Improvement
            Reporter: Justinwins


When there is a node NOT available,we found a lot of log like :

[2022-07-12 17:05:26.403] [WARN] [kafka-admin-client-thread | adminclient-20] [c.v.p.middleware.kafka.clients.NetworkClient] >>> [AdminClient clientId=adminclient-20] Connection to node -1 could not be established. Broker may not be available.

 

If the app uses many admin clients when it connects many kafka clusters , it would be no easy thing to get exactly the crashed node as no node name or listener name

is in the log. 



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