Kafka fails to start: Zookeeper namespace does not exist about zetcd HOT 4 CLOSED

You should create namespaces manually, kafka can't do it automatically for some reason:

zkctl create '/' ''
zkctl create '/brokers' ''
zkctl create '/brokers/ids' ''
zkctl create '/brokers/topics' ''

from zetcd.

@corpix Kafka should automatically create the chroot path (if it does not exist) since 0.8.2.0. See KAFKA-404. I've been using these Kafka images and they have always created the chroot (since 0.9.0.0).

I think in this case, it is because zetcd does not create the / node by default, which is why zkui also complains about the missing root node on a fresh zetcd and etcd setup.

from zetcd.

@F21 Send a pr to fix it? thank you!

from zetcd.

Hey @xiang90 Unfortunately, I am not too familiar with the code and am super swamped at the moment, so I am not sure if I'll have the time to make a PR.

However, I don't think this is easily fixed by just creating the root node. For example, currently, zetcd does not complain if etcd is not accessible. This is useful if we start etcd and zetcd using docker-compose and zetcd starts up much faster than etcd. In this case, zetcd would probably need to implement some sort of retry and timeout policy when attempting to create this root node.

from zetcd.