Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com
 designates 209.85.223.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1370954912393-7578740.post@n2.nabble.com>
References: <1370954912393-7578740.post@n2.nabble.com>
From: Ted Dunning <ted.dunning@gmail.com>
Date: Tue, 11 Jun 2013 22:30:59 +0200
Message-ID: 
 <CAJwFCa34imG-HpWPYHCjvGxqLEHoLhCEoMR4UV2_FFCPNpHggw@mail.gmail.com>
Subject: Re: ZooKeeper survives 4 nodes, dies with 3
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Cc: "zookeeper-user@hadoop.apache.org" <zookeeper-user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=047d7b10ca552f704204dee6c8b3

--047d7b10ca552f704204dee6c8b3
Content-Type: text/plain; charset=UTF-8

This sounds like you have a bad configuration for your cluster.


On Tue, Jun 11, 2013 at 2:48 PM, NoamBC <noam@cloudon.com> 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.
>

--047d7b10ca552f704204dee6c8b3--