Robin Moffatt • 1/3/2018

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

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