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
Webinar Series – SQL Server Indexing
Koen Verbeeck • 2 votes
2
Risks and Limitations of AI in the Life Sciences
Jeremy Howard • 2 votes
3
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 2 votes
4
1M context is now generally available for Opus 4.6 and Sonnet 4.6
Simon Willison • 1 votes
5
AI is my CMS
Chris Coyier • 1 votes
6
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes