When a connectionloss happens all the watches are triggered saying that
connectionloss occurred. But on a reconnect the watches are reset
automagically  on the new server and will be fired if the change has already
happened or will be reset!

I hope that answers your question.


On 6/30/10 5:11 PM, "Ted Dunning" <ted.dunn...@gmail.com> wrote:

> I think that you are correct, but a real ZK person should answer this.
> On Wed, Jun 30, 2010 at 4:48 PM, Bryan Thompson <br...@systap.com> wrote:
>> For example, if a client registers a watch, and a state change which would
>> trigger that watch occurs _after_ the client has successfuly registered the
>> watch with the zookeeper quorum, is it possible that the client would not
>> observe the watch trigger due to communication failure, etc., even while the
>> clients session remains valid?  It sounds like the answer is "no" per the
>> timeliness guarantee.  Is that correct?

Reply via email to