Isn't it the case that the client won't get session expired until it's
able to connect to a server, right? So what might happen is that the
client loses connection to the server, the server eventually expires the
client and deletes ephemerals (notifying all watchers) but the client
won't
Why is it done that way? How am I supposed to reliably detect that my
ephemeral nodes are gone? Why not deliver the Session Expired event on the
client side after the right time has passed without communication to any
server?
On Thu, Mar 26, 2009 at 10:58 AM, Mahadev Konar
The problem is that we cannot differentiate between the servers being down
and a network problem from the client to servers.
If the servers are down and we expire the session for a client on the client
side -- the servers would come up and would still have the session as valid
(though it will be
its own ephemeral nodes
for 15 seconds.
ben
From: Nitay [nit...@gmail.com]
Sent: Thursday, March 26, 2009 12:09 PM
To: zookeeper-user@hadoop.apache.org
Subject: Re: Semantics of ConnectionLoss exception
Why is it done that way? How am I supposed to reliably
I'm a little unclear about the ConnectionLoss exception as it's described in
the FAQ and would like some clarification.
From the state diagram, http://wiki.apache.org/hadoop/ZooKeeper/FAQ#1, there
are three events that cause a ConnectionLoss:
1) In Connecting state, call close().
2) In Connected
Hi Nitay,
- Does this event happening mean my ephemeral nodes will go away?
No. the client will try connecting to other servers and if its not able to
reconnect to the servers within the remaining session timeout.
If the client is not able to connect within the remaining session timeout,
the
Mahadev Konar wrote:
Hi Nitay,
- Does this event happening mean my ephemeral nodes will go away?
No. the client will try connecting to other servers and if its not able to
reconnect to the servers within the remaining session timeout.
If the client is not able to connect within the
