> 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 <[email protected]> wrote: > Hi everyone! The zk API's sync() method brings the server up to date with > the leader. So the next client read should give the up to date value. But > in the time between completing the sync and starting the read, another client > 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 guaranteeing 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 communication in > error) please notify the sender immediately and destroy this communication. > 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 > contained in this communication should not be regarded as such.
