Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: zookeeper-user@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns;
	h=message-id:date:from:user-agent:mime-version:to:subject:
	references:in-reply-to:content-type:content-transfer-encoding;
	b=CBkXR2QJ2V3xcWw5n59hBtPo208qae2nib6ma1+PP7BVBbjRW3wA418OFMdnrxJi
Message-ID: <4C45C776.8060307@yahoo-inc.com>
Date: Tue, 20 Jul 2010 08:57:42 -0700
From: Benjamin Reed <breed@yahoo-inc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.10) Gecko/20100527 Thunderbird/3.0.5
MIME-Version: 1.0
To: zookeeper-user@hadoop.apache.org
Subject: Re: does a ZK client read its own write
References: <AANLkTilUI9pjbiTK9wuS79Qgp0cVlvQD2zg8I7cNzbvc@mail.gmail.com>
In-Reply-To: <AANLkTilUI9pjbiTK9wuS79Qgp0cVlvQD2zg8I7cNzbvc@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

it is still guaranteed to see its own write. when a client reconnects to 
a different server, we guarantee that the new server will be at least as 
up-to-date as the last server. otherwise the client would go back in 
time and a lot of things would go wrong.

ben

On 07/20/2010 08:28 AM, Jun Rao wrote:
> Hi,
>
> In ZK, a read is handled by any server while a write is broadcasted from the
> leader. If a client writes x to /X and then reads /X, is the client
> guaranteed to see its own write x (what if a connection loss event happens
> after the write and before the read)? Thanks,
>
> Jun
>