How to solve Connection to node -1 could not be established. Broker may not be available during Kafka debugging

  • 的头像-Tumi
  • 42 day agopublish

This article mainly explains “How to solve Connection to node -1 could not be established. Broker may not be available during kafka debugging”. The explanation in the article is simple and clear, easy to learn and understand, please follow The editor’s thoughts are slowly deepening, let’s study and learn “How to solve Connection to node -1 could not be established. Broker may not be available during kafka debugging”!

Kafka error content:

WARN [Consumer clientId=consumer-1, groupId=console-consumer-950] Connection to node -1 could not be established. Broker may not be available.

This is because the PLAINTEXT in your configuration file is different from the content you requested. For example, I configured listeners=PLAINTEXT://10.127.96.151:9092 in the configuration file, but when I want to test, the request is ./kafka-console-consumer.sh –bootstrap-server localhost:9092- -topic topic1 –from-beginning

The correct one should be ./kafka-console-consumer.sh –bootstrap-server 10.127.96.151:9092 –topic topic1 –from-beginning

Thank you for reading, the above is the content of “How to solve Connection to node -1 could not be established. Broker may not be available” during kafka debugging. After studying in this article, I believe You have a deeper understanding of how to solve this problem when you encounter Connection to node -1 could not be established. Broker may not be available during kafka debugging. The specific usage needs to be verified by everyone. This is Tumi Cloud. The editor will push more articles about relevant knowledge points for everyone, welcome to pay attention!

© Copyright Notice
THE END
Just support it if you like
like0
share
comment Grab the couch

Please log in to comment