Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of devaki.vamsi@gmail.com
 designates 209.85.216.48 as permitted sender)
MIME-Version: 1.0
References: <2014103111214762407717@163.com>
From: Vamsi Devaki <devaki.vamsi@gmail.com>
Date: Fri, 31 Oct 2014 03:37:46 +0000
Message-ID: 
 <CAFuMMGRpJ3NYpXwaS9TY8VmWeOcD0Hmsjt6VWD3VgnSKd93Q=g@mail.gmail.com>
Subject: Re: How zookeeper handles the split-brain scenario
To: user <user@zookeeper.apache.org>
Content-Type: multipart/alternative; boundary=001a11c13cae6900a70506afb864

--001a11c13cae6900a70506afb864
Content-Type: text/plain; charset=UTF-8

Zookeeper needs at least quorum to operate. Any partition that is smaller
than quorum will not be able to make any state changes.

On Thu Oct 30 2014 at 8:24:53 PM bit1129@163.com <bit1129@163.com> wrote:

> Hi Zookeepers,
> I am wondering the mechanism that zookeeper takes to handle the
> split-brain scenario :  two or more parts of the system make progress
> independently, leading to inconsistent behavior.
> Looks to me that as long as the mojority of the assemble are still
> working, there would no split brain problem? but I don't clear
> understanding on this, and also could not understand how it keep the
> assemble in consistent state.
>
> Could someone explain this?
>
> Thanks!
>
> -Todd
>

--001a11c13cae6900a70506afb864--