Cannot get consumer group list for cluster <name>: zk: node does not exist about burrow HOT 6 CLOSED

It sounds like your configuration in Burrow for Zookeeper is not correct. Burrow does not use the Zookeeper information to discover the Kafka cluster, it uses the defined broker list to do that.

Please post your configuration section for the cluster.

from burrow.

Hello Todd, here's my configuration:

[zookeeper]
hostname=zookeeper0
hostname=zookeeper1
hostname=zookeeper2
hostname=zookeeper3
hostname=zookeeper4
port=2181
timeout=6
lock-path=/burrow/notifier

[kafka "prod"]
broker=kafka0
broker=kafka1
broker=kafka2
broker-port=6667
zookeeper=zookeeper1
zookeeper=zookeeper2
zookeeper=zookeeper3
zookeeper=zookeeper4
zookeeper=zookeeper5
zookeeper-port=2181
zookeeper-offsets=true
zookeeper-path=/util/kafka-logging

I can ping zookeeper* hosts from my machine and can telnet to port 2181.

from burrow.

So that error is generated when Burrow is unable to get child znodes for /util/kafka-logging/consumers Can you check that that znode exists on your ensemble with that exact path?

from burrow.

Yes, I have verified in Zookeeper Exhibitor that this path exists. Moreover (I failed to mention this before)

kafka-consumer-offset-checker.sh --zookeeper zookeeper0:2181/util/kafka_logging --group scu17

works and returns proper lags and offsets. That's why I had a suspicion that something is up with Burrow.

from burrow.

Your offset checker command does not match the Zookeeper path you specified in your config. Your config shows /util/kafka-logging. Your command has /util/kafka_logging

from burrow.

Doh, this is embarrassing! I stared at this config for too long. This was indeed an issue. Thanks, Todd!

from burrow.