search

alexguan / node-zookeeper-client

A pure Javascript ZooKeeper client for Node.js
Other
539 stars 147 forks source link

NO_NODE exception when using connect string with multiple chroot'd servers #24

Open chriscapaci opened 10 years ago

chriscapaci commented 10 years ago

So, as the title says, I'm seeing an exception when I attempt to use a client instance that has successfully connected when it includes multiple servers. These servers all contain a chroot path, but I'm not sure if that makes a difference in the issue or not. I assume that you have tried this module out with multiple servers, but maybe not multiple servers chroot'd? The chroot path is the same for all servers, so that doesn't matter.

The connection succeeds, I handle the 'connected' event, but when I attempt to do anything after that, for example I try to do a mkdirp in the 'connected' handler to initialize things, it fails with NO_NODE exception. I tried following things down through the jute code, but I couldn't find anything that would send back a NO_NODE error.

I don't know what 'node' the error is referring to and I don't know why things work with one server in the connect string, but not with multiple servers. Can anyone help me out? Thanks.

alexguan commented 10 years ago

Has this been resolved by #25 ?