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
Not sure if it's just my problem or not. I am using the provided docker-compose.yml example in the documentation. When I started on local, all 3 containers started up, but when I went into containers themselves and ran ./zkServer.sh status, all of them gave me the following output:
ZooKeeper JMX enabled by default
Using config: /conf/zoo.cfg
Client port not found in static config file. Looking in dynamic config file.
grep: : No such file or directory
Client port not found. Terminating.
zookeeper cannot start
But then when I switch zookeeper version to 3.4, everything works perfectly, zookeeper starts correctly, I can connect to each of the node using zkCli.sh
Expected behavior
Using the provided docker-compose.yml example with zookeeper:3.5 on local, zookeeper should start correctly, no port issue
The issue is that the client port part is missing in ZOO_SERVERS. E.g., for zoo1 it should have been ZOO_SERVERS: server.1=0.0.0.0:2888:3888;2181 server.2=zoo2:2888:3888;2181 server.3=zoo3:2888:3888;2181.
Not sure if it's just my problem or not. I am using the provided
docker-compose.yml
example in the documentation. When I started on local, all 3 containers started up, but when I went into containers themselves and ran./zkServer.sh status
, all of them gave me the following output:zookeeper cannot start
But then when I switch zookeeper version to 3.4, everything works perfectly, zookeeper starts correctly, I can connect to each of the node using
zkCli.sh
Expected behavior
Using the provided
docker-compose.yml
example with zookeeper:3.5 on local, zookeeper should start correctly, no port issueActual behavior
Cannot find port
Steps to reproduce the behavior
and run
docker-compose up -d
bin
folder, and ran./zkServer.sh status
System configuration
MacBook Pro
Intel Core i7
Memory: 16 GB
The text was updated successfully, but these errors were encountered: