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 start on a resource, and an error message similar to the following example is displayed:
CDISA5309E ZooKeeper was not started on host1.ibm.com:40740 since it is running on a different host host2.ibm.com.
Check to see if the embedded ZooKeeper server process is running on the other resource.
To list the processes, enter the following command:
ps uxww | grep zookeeper
  • If the server process (com.ibm.streams.zookeeper.StreamsQuorumPeer) is running, stop embedded ZooKeeper on the other resource by entering streamtool embeddedzk --stop. Then start embedded ZooKeeper on the current resource by entering streamtool embeddedzk --start.

  • If embedded ZooKeeper is not running on the other resource and the problem still occurs, delete the zookeeper_server.host file. This file is located in the directory that is specified on the streams.zookeeper.property.dataDir bootstrap property. Then start embedded ZooKeeper on the current resource by entering streamtool embeddedzk --start.