Ben,
Thank you, I now see the rationale in not telling the client it's session is
over because you can't be sure it actually is. But would it make sense to
add a new state in KeeperState representing that corner case? Something like
AfterSessionTimeout. I'm pretty sure other would find that useful
ZooKeeper only tells you about states that it is sure about, so you will
not get the Expired event until you reconnect to ZooKeeper. if you never
connect again to ZooKeeper, you will not get the Expired event. if you
want to timeout using some sanity value, 2 times the session timeout for
examp
Hey all,
Working on integrating HBase with ZK, we came around an issue that we
are unable to resolve. I was trying to see how was our handling of
network partitions and session expirations and what I did is just
starting a single ZK instance with a very simple HBase setup, then I
killed the ZK ser
+1 to this idea. It will be good to have some more focus on examples of how
to build applications using ZK; experiences here will feed back into the
design of the core.
Henry
On Tue, Jun 23, 2009 at 2:23 AM, Mahadev Konar wrote:
> Hi Stefan,
> This would be a good addition. Feel free to open a
