Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # user >> Restarting leader zookeeper instance made quorum lost


Copy link to this message
-
Re: Restarting leader zookeeper instance made quorum lost
On Wed, Apr 9, 2014 at 12:56 PM, Bae, Jae Hyeon <[EMAIL PROTECTED]> wrote:
Yes.

No.

You have to always have 3 ZK nodes live in order to maintain continuous
operation.

Rolling restart implies that you wait long enough after restarting each
node so that it has a chance to rejoin the quorum.  If you do that then
restarting the leader will result in a tiny moment when writes will not be
accepted and may require some ZK clients to transparently reconnect to a
different ZK node, but it should be hard to detect any outage.
 
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