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: local policy)
From: Adrian Osullivan <adrian.osullivan@db.com>
To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
Date: Tue, 5 Nov 2013 13:38:06 -0600
Subject: RE: Sync question
Thread-Topic: Sync question
Thread-Index: Ac7aXlxiL0dL3tS4QmO7niH4vYgnawAABAgw
Message-ID: 
 <E0699BDD1C95EC4190CF27C12C6D72DD0102DE755016@USTLCDBG001.US.DB.COM>
References: 
 <E0699BDD1C95EC4190CF27C12C6D72DD0102DE75500D@USTLCDBG001.US.DB.COM>
 <DE3D23FE-2FBF-4921-BF34-30D134B62D15@jordanzimmerman.com>
In-Reply-To: <DE3D23FE-2FBF-4921-BF34-30D134B62D15@jordanzimmerman.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks, just wanted to confirm that. Some of the things you read about sync=
 seem to suggest the next client read will be up to date but this is not st=
rictly true.  This isn't a fault of course, but by design.

-----Original Message-----
From: Jordan Zimmerman [mailto:jordan@jordanzimmerman.com]
Sent: Tuesday, November 05, 2013 2:36 PM
To: user@zookeeper.apache.org
Subject: Re: Sync question

> So it seems there is no mechanism is zookeeper for guaranteeing a read is=
 truly up to date with the leader. Is this true?

ZooKeeper is an eventually consistent system, not an ACID system. So, true.

On Nov 5, 2013, at 11:31 AM, Adrian Osullivan <adrian.osullivan@db.com> wro=
te:

> Hi everyone!  The zk API's sync() method brings the server up to date wit=
h the leader.  So the next client read should give the up to date value.  B=
ut in the time between completing the sync and starting the read, another c=
lient may have sent an update and the server one is connected to may again =
lag the leader.  So it seems there is no mechanism is zookeeper for guarant=
eeing a read is truly up to date with the leader. Is this true?
>
> ---
> This communication may contain confidential and/or privileged information=
. If you are not the intended recipient (or have received this communicatio=
n in error) please notify the sender immediately and destroy this communica=
tion. Any unauthorized copying, disclosure or distribution of the material =
in this communication is strictly forbidden.
>
> Deutsche Bank does not render legal or tax advice, and the information co=
ntained in this communication should not be regarded as such.


---
This communication may contain confidential and/or privileged information. =
If you are not the intended recipient (or have received this communication =
in error) please notify the sender immediately and destroy this communicati=
on. Any unauthorized copying, disclosure or distribution of the material in=
 this communication is strictly forbidden.

Deutsche Bank does not render legal or tax advice, and the information cont=
ained in this communication should not be regarded as such.