Thanks Neha,

I see now that is true.  It looks like it just needs to resolve all the
hosts (but doesn't need zk to be available on each host).  So
decommissioning a zknode (and removing from dns) is a bit more sensitive
than I thought.  I can't think of any reason that zkClient should require
this behavior, other than for keeping clean configurations.  But it makes
it difficult to roll in new changes to the cluster layout while keeping
services up.

On Tue, May 21, 2013 at 2:20 PM, Neha Narkhede <[EMAIL PROTECTED]>wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB