Robin Moffatt • 1/3/2018

Kafka - AdminClient - Connection to node -1 could not be established. Broker may not be available

Read Original

The article details a specific Apache Kafka error: 'Connection to node -1 could not be established. Broker may not be available.' It explains the root cause as a networking configuration mismatch where Kafka services (Schema Registry, Connect) default to localhost while Kafka itself listens on a specific hostname IP. The solution involves correcting properties files and the /etc/hosts configuration.

0 comments
#configuration #networking #Troubleshooting
Kafka - AdminClient - Connection to node -1 could not be established. Broker may not be available

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Top picks — 2026 January
Paweł Grzybek • 1 votes
3
In Praise of –dry-run
Henrik Warne • 1 votes
4
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
5
Vibe coding your first iOS app
William Denniss • 1 votes
6
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
7
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes