Thanks, that answers the second part of my question. However im still
unclear as to when the DISCONNECTED event will be received. Im currently
assuming that Ill get it immediately after the connection is lost.
On Tue, Apr 10, 2012 at 10:34 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 10, 2012 at 6:41 PM, Rohan Desai <[EMAIL PROTECTED]>
> > Im new to zk and had some questions about connection loss events. From
> > I understand when a ZK handle loses connection to the ZK cluster, the ZK
> > client's watch handler receives a DISCONNECTED event. If the connection
> > lost for longer than the session timeout, the ZK client's watch handler
> > receives a SESSION_EXPIRED event and the handle is closed. If this is
> > correct, does the ZK client's watch handler receive the DISCONNECTED
> > right after the client loses its connection to the cluster? When does the
> > client get the SESSION_EXPIRED event? Does it get it after the client
> > detects the session would have timed out or only after the client is able
> > to re-establish a connection to the ZK cluster?
> Some good details in the faq on this:
> It's not exactly as you describe - for example you can't know the
> session is expired until you reconnect to the server.
> Also see this section in the programmer guide: