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 bitanarch@gmail.com
 designates 209.85.160.54 as permitted sender)
References: 
 <CACeqxwTkKFvXUQOit0r41asMQGb8fQHP5wGQtocQjG8knKy91g@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: 
 <CACeqxwTkKFvXUQOit0r41asMQGb8fQHP5wGQtocQjG8knKy91g@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A4A256C-89B9-4088-9919-655BDFFC3F71@gmail.com>
Cc: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
From: Martin Kou <bitanarch@gmail.com>
Subject: Re: issue about write sync in majority followers
Date: Thu, 5 Sep 2013 21:11:59 -0700
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>

The follower doesn't persist in the beginning - not until it's sure it had t=
he consensus of the quorum. Also, the client only talks to the node it is co=
nnected to.

The general algorithm you're looking for here is Paxos. You may want to look=
 that up.

Sent from my iPhone

> On Sep 3, 2013, at 11:54 PM, ch huang <justlooks@gmail.com> wrote:
>=20
> hi,all:
>          i am very confused about the write sync  process,what i thank is
> ,client connect to one of follower ,send a update request to it,and the
> follower persisted the update to it's disk ,then forward this request to
> the leader,the leader broadcast it to all it's follower, if the leader get=

> responce of the majority of all follower say the update succeed, it commit=
s
> the update ,and the client will get success response (from who? the leader=

> or the follower who connected?)
>=20
> so before leader persisted the change ,this change should be persisted on
> majority of followers ?
>=20
> what i think is right??