Hi Todd -
The general explanation for why Zookeeper doesn't pass the event information
w/ the event notification is that an event notification is only triggered
once, and thus may indicate multiple events. For example, if you do a
GetChildren and set a watch, then multiple children are added at
All,
I'm working on a ZK deployment that will support a heterogeneous set of
processes connecting to the ZK and creating ephemeral nodes. We have the
conflicting requirements that:
a) If a process crashes (closes its socket) without calling a proper
close, we would like the ephemeral node
I think he's saying that if the socket closes because of a crash (i.e. not a
normal zookeeper close request) then the session stays alive until the
session timeout, which is of course true since ZK allows reconnection and
resumption of the session in case of disconnect due to network issues.
On Mon, Aug 30, 2010 at 1:11 PM, Avinash Lakshman
avinash.laksh...@gmail.com wrote:
From my understanding when a znode is updated/created a write happens into
the local transaction logs and then some in-memory data structure is
updated
to serve the future reads.
Where in the source code can
Yes that's right. Which network issues can cause the socket to close without
the initiating process closing the socket? In my limited experience in this
area network issues were more prone to leave dead sockets open rather than vice
versa so I don't know what to look out for.
Thanks,
Camille
Depending on your classpath setup:
java org.apache.zookeeper.ZooKeeperMain -server 127.0.0.1:2181
if jline jar is in your classpath (included in the zk release
distribution) you'll get history, auto-complete and such.
Patrick
On 08/31/2010 03:08 PM, Michi Mutsuzaki wrote:
Hello,
I'm
Hi Dave,
Thanks for the response. I understand your point about missed events
during a watch reset period. I may be off, here is the functionality I
was thinking. I'm not sure if the ZK internal versioning process could
possibly support something like this.
1. A watch is placed on children
