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 >> ZooKeeper survives 4 nodes, dies with 3


Copy link to this message
-
Re: ZooKeeper survives 4 nodes, dies with 3
This sounds like you have a bad configuration for your cluster.
On Tue, Jun 11, 2013 at 2:48 PM, NoamBC <[EMAIL PROTECTED]> wrote:

> Hi,
>
> We use ZK 3.3 in production, a quorum of 5 nodes, and found an odd
> behaviour
> where if we take one node offline, the quorum keeps serving requests, but
> if
> we take another node offline, it stops working.
>
> Reading the ZK documentation, it seems it should still work with 3 nodes,
> allowing us to lose 2 nodes, but in practice we can only lose 1 node until
> we have downtime.
>
> Is this a bug which was fixed in later versions?
> Has anyone seen this happen?
>
> Thanks,
> Noam.
>
>
>
>
>
> --
> View this message in context:
> http://zookeeper-user.578899.n2.nabble.com/ZooKeeper-survives-4-nodes-dies-with-3-tp7578740.html
> Sent from the zookeeper-user mailing list archive at Nabble.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