IBM Streams 4.2

ZooKeeper problems and solutions

Use these solutions to resolve the problems that you might encounter with Apache ZooKeeper.

Notes:

This information applies to both external ZooKeeper and embedded ZooKeeper unless otherwise indicated.
Java™ Version 6, or later is required to run ZooKeeper.

ZooKeeper log files, documentation, and other troubleshooting resources
These resources provide additional assistance and information for resolving problems with ZooKeeper.
ZooKeeper ensemble fails to start
ZooKeeper might fail to start if the ZooKeeper ensemble is not configured correctly, or there are problems with file permissions, port conflicts, or disk corruption.
Embedded ZooKeeper fails to start
In a shared file system environment, embedded ZooKeeper can fail to start if it is already running on another resource.
Embedded ZooKeeper fails to stop
If you cannot stop the embedded ZooKeeper, you can force the processes to stop.
Unable to connect to the ZooKeeper ensemble
You might not be able to connect to the ZooKeeper ensemble if you exceeded the maximum number of connections, or there are network, host, or ZooKeeper problems.
Clients disconnect from the ZooKeeper ensemble
Clients, such as IBM® Streams interfaces and services, might disconnect from ZooKeeper for various reasons. For example, this problem occurs if the network is down, memory errors occurred, or embedded ZooKeeper restarted.

Parent topic: Known problems and solutions