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: domain of bitanarch@gmail.com designates
 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAB91ZrPk+TNbiismVj6E5QfHfaZbjWuo9fmMDRHDFP10fovG9Q@mail.gmail.com>
References: 
 <CAB91ZrMuTYs+5GFSXotCT6CigTEHdG9JHW6DEUrerwRN3C0J2A@mail.gmail.com>
	<CABWqe2bk8i+Lz8V=wcnyRx69MNRBacBvwke9AzxPbTfVCiJWzg@mail.gmail.com>
	<CAB91ZrPk+TNbiismVj6E5QfHfaZbjWuo9fmMDRHDFP10fovG9Q@mail.gmail.com>
Date: Sat, 19 May 2012 14:31:16 -0700
Message-ID: 
 <CAP1VaJt15zkLGvkTCB8ODBw8eY1p_8jJzxAV8Cp9Z-bRVUK-wQ@mail.gmail.com>
Subject: Re: How to recover previous watcher & event after "session expired"
From: Martin Kou <bitanarch@gmail.com>
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=f46d04428edc9a5ca404c06a6331

--f46d04428edc9a5ca404c06a6331
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Correct. And even simple connection losses can cause watches to become
unreliable as well:

http://zookeeper.apache.org/doc/trunk/releasenotes.html#Watch+Management
"One caveat to the watch management: it is possible to miss an event for
the creation and deletion of a znode if watching for creation and both the
create and delete happens while the client is disconnected from ZooKeeper."

Best Regards,
Martin Kou

On Fri, May 18, 2012 at 8:33 PM, =C0=EE=BA=D5=D4=AA <liheyuan.bj@gmail.com>=
 wrote:

> Thanks for your help.
> That means we can't totally rely on watchs because it may loss event if
> session expired, right?
>
> =D4=DA 2012=C4=EA5=D4=C219=C8=D5=D0=C7=C6=DA=C1=F9=A3=ACCamille Fournier =
<camille@apache.org> =D0=B4=B5=C0=A3=BA
> > I'm not sure what you mean in question #1. A session expired event
> > generally causes the client to become completely invalid, you could
> > wrap the client in your own logic to record what you were watching,
> > but I don't think you can get that out of the client after it's
> > expired.
> >
> > 2. You won't be able to see events that happened when the session was
> > expired. The server has closed your connection and won't know to send
> > you events unless you have a valid session with a valid watch.
> >
> > 3. Reconnect won't work on expired sessions, you need to create an
> > entirely new session. Reconnect works when you get disconnected but
> > not expired.
> >
> > Hope that helps
> > On Fri, May 18, 2012 at 12:18 PM, =C0=EE=BA=D5=D4=AA <liheyuan.bj@gmail=
.com> wrote:
> >> Hi, All
> >>
> >> I'm dealing with the case of "session expired" event. Please help me
> >> with the following question.
> >>
> >> 1. After receive "session expired" event, how to recover the watch
> >> that are setting before expired gracefully?
> >>
> >>
> >> 2.Currently, I record the watch setting and call the api to set it
> >> again after I got "expired event". It will callback for event after
> >> connection was success again. But what about the event happend between
> >> I success reinit the session to zk server. Currently, it got lost. Is
> >> there any way that I can got these events ?
> >>
> >>
> >> 3.I try to use reconnect, in zookeeper_init, but does't work. My guess
> >> is reconnect is only work for connection that are in state connect
> >> (Not valid after session timeout), is it right?
> >>
> >>
> >> Thanks for your help !
> >
>

--f46d04428edc9a5ca404c06a6331--