I'm trying to startup a quorum of Zookeeper servers in a cluster,
however, Zookeeper is failing to start because it cannot find its
hostname in the list of Zookeeper quorum servers.

I know this problem is well documented on the WIKI, however, my
situation is a little different. The allocation of a node to become a
Zookeeper is done dynamically by a management service running else where
on the cluster. This node then associates its IP with a hostname in the
Zookeeper quorum list. The hostname is not the default hostname of the
node. The node may associate its IP with multiple hostnames for each
service that it is allocated.

This causes a problem when Zookeeper starts. Zookeeper does a
getdefaulthost which will return the nodes default hostname and not the
associated hostname.

So my questions are:

1. Is it possible to resolve this some other way? We are not running DNS
(hostname associations are managed by our own services). We also cannot
use the nodes ip address as the nodes are allocated dynamically.
Dynamically updating the config files is also not practical. 

2. Why does Zookeeper need to test whether its hostname is in the
Zookeeper quorim list? Can this safely be disabled?

Richard


Reply via email to