Kafka Consumer: No entry found for connection

Question

I am trying to check the kafka consumer by consuming the data from a topic on a remote Kafka cluster. I am getting the following error when I use the kafka-console-consume

Answer 1

In my case I was receiving that while trying to connect to my Kafka container, I had to pass the following:

-e KAFKA_LISTENERS=PLAINTEXT://0.0.0.0:9092

-e KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://localhost:9092

Hope it helps someone

Answer 2

I have found the problem. It was a DNS problem at the end. I was reaching out the Kafka brokers by the IP addresses, but the broker replies with DNS name. After setting the DNS names on the consumer side, it started working again.

Answer 3

In my case, it was not able to find broker id (2147475658) mentioned in error.

No entry found for connection 2147475658

You can create a broker with id 2147475658 by setting broker.id property in server.properties file. Create separate server.properties files for all brokers.

Or If you have at least one alive broker, then you can delete/remove broker which is giving error.

Documentation Link : https://kafka.apache.org/documentation/#quickstart_multibroker

Answer 4

Are you sure the remote kafka is running. I would suggest running nmap -p PORT HOST in order to verify the port is open (unless it is configured differently the port should be 9092). If that is ok, then you can use kafkacat which makes things easier. Create a consumer running kafkacat -b HOST:PORT -t YOUR_TOPIC -C -o beginning or create a producer running kafkacat -b HOST:PORT -t YOUR_TOPIC -P

Answer 5

I had this problem (with consumers and producers) when running Kafka and Zookeeper as Docker containers.

The solution was to set advertised.listeners in the config/server.properties file of the Kafka brokers, so that it contains the IP address of the container, e.g.

advertised.listeners=PLAINTEXT://172.15.0.8:9092

See https://github.com/maxant/kafkaplayground/blob/master/start-kafka.sh for an example of a script used to start Kafka inside the container after setting up the properties file correctly.

Answer 6

It seems the Kafka cluster listener property is not configured in server.properties.

In the remote kafka cluster, this property should be uncommented with the proper host name.

listeners=PLAINTEXT://0.0.0.0:9092