You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 7, 2023. It is now read-only.
@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.
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.
I have a Kafka 0.11 and Zookeeper 3.4 setup running flawlessly in docker.
I want to replace Zookeeper with etcd and zetcd.
This is the error I get when I start kafka:
If I use zkui to browse the zetcd server, it gives this warning when connecting to zetcd:
get(/) failed, err=node not exists
.I think this is because zetcd does not create the root node by default, resulting in kafka not being able to create its chroot node.
If I run zookeeper and access it using zkui, I do not get that error, and there is also a
zookeeper
child node.The text was updated successfully, but these errors were encountered: