If one of your user clients can no longer reach one member of the ZK cluster, then it will try to reach another. If it succeeds, then it will continue without any problems as long as the ZK cluster itself is OK.
This applies for all the ZK recipes. You will have to be a little bit careful to handle connection loss, but that should get easier soon (and isn't all that difficult anyway). On Fri, Apr 30, 2010 at 1:26 PM, Lei Gao <l...@linkedin.com> wrote: > I am not talking about the leader election within zookeeper cluster. I > guess > I didn't make the discussion context clear. In my case, I run a cluster > that > uses zookeeper for doing the leader election. Yes, nodes in my cluster are > the clients of zookeeper. Those nodes depend on zookeeper to elect a new > leader and figure out what the current leader is. So if the zookeeper > (think > of it as a stand-alone entity) becomes unavailabe in the way I've described > earlier, how can I handle such situation so my cluster can still function > while a majority of nodes still connect to each other (but not to the > zookeeper)? >