Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: zookeeper-user@hadoop.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns;
	h=received:user-agent:date:subject:from:to:message-id:
	thread-topic:thread-index:in-reply-to:mime-version:content-type:
	content-transfer-encoding:return-path:x-originalarrivaltime;
	b=eZqbiPeMZ21bWqYP47SVwPY9R6W9IPJEdb33xQyO6I1gvmEjxE7dYNo1XhAdkwla
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Tue, 06 Jan 2009 19:12:16 -0800
Subject: Re: Simpler ZooKeeper event interface....
From: Mahadev Konar <mahadev@yahoo-inc.com>
To: <zookeeper-user@hadoop.apache.org>
Message-ID: <C5895D90.165C7%mahadev@yahoo-inc.com>
Thread-Topic: Simpler ZooKeeper event interface....
Thread-Index: Aclwdb4fHhqNUrFJBkK8xtfWnbOHMQ==
In-Reply-To: <30c6373b0901061657y61d329e4m73745c4f3a18ef8a@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

http://issues.apache.org/jira/browse/ZOOKEEPER-23

This has been fixed in zookeeper-3.0 release. Are you using a release from
sourceforge?


mahadev


On 1/6/09 4:57 PM, "Kevin Burton" <burton@spinn3r.com> wrote:

> This could be simplified if the semantics for reconnect were simplified.
> Is there any reason why I should know about a disconnect if ZK is just going
> to reconnect me to another server in 1ms?
> 
> Why not hide *all* of this form the user and have the client re-issue
> watches on reconnect and hold off on throwing exceptions if the server
> returns.
> 
> This would allow the user to just handle three conditions... total ensemble
> failure, no ACL permission, or no node existing (of vice-versa).
> 
> Kevin
> 
> 
>> If I run an async request, the client should replay these if I'm
>> reconnected to another host.
>> 
>> --
> Founder/CEO Spinn3r.com
> Location: San Francisco, CA
> AIM/YIM: sfburtonator
> Skype: burtonator
> Work: http://spinn3r.com