DEV Community

loading...

Kafka Connect - Failed to select new Group Coordinator when one dies

vipinkh97 profile image Vipin Dhonkaria ・1 min read

I am having 4 nodes Kafka cluster and one zookeeper node running. When group coordinator dies then zookeeper won't select new group coordinator from available brokers list instead it keeps trying discovering the died Kafka broker. It stopped the Kafka connectors from pushing events from Kafka topic to elastic search index.

Kafka Cluster : host1:9092, host2:9092, host3:9092, host4:9092

zookeeper node = host4:2181
group coordinator = host4:9092
broker id = 0 , host1:9092
broker id = 1 , host2:9092
broker id = 2 , host3:9092
broker id = 3 , host4:9092
zookeeper is not assigning a new group coordinator and respond Disconnect connection.

2019-12-26 16:01:15 INFO AbstractCoordinator:780 - [Worker clientId=connect-1, groupId=kafkaconnector] Group coordinator host4:9092 (id: 2147483647 rack: null) is unavailable or invalid, will attempt rediscovery
2019-12-26 16:01:16 INFO FetchSessionHandler:442 - [Consumer clientId=consumer-2, groupId=kafkaconnector] Error sending fetch request (sessionId=2112463313, epoch=INITIAL) to node 0: org.apache.kafka.common.errors.DisconnectException.
Also I am not able to fetch events from Kafka topics from console-consumer when group coordinator is dead.

On executing ./kafka-console-consumer.sh --bootstrap-server node2:9092 --topic connector

I am getting this warning response continuously and won't get messages from Kafka topics.

[2019-12-26 16:35:30,909] WARN [Consumer clientId=consumer-1, groupId=console-consumer-20067] Connection to node -1 (/node4:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
I am not able to fix it from last week. Please help on the same.

Discussion (0)

pic
Editor guide