I have an application that uses ZooKeeper. There is an ensemble in
production. But in order to simplify development the application will
start an embedded ZooKeeper server when started in development mode. We
are experiencing a timing issue with ZooKeeper 3.3.3 and I was wondering
if this is allowed to be happen or if we did something wrong when
starting the embedded server.
Basically, we have a watch registered using an #exists call and watch
code like the following.
From inspecting the logs we noticed a NoNodeException. When setting
breakpoints on #loadNode and stepping through we don't get the
exception. But when setting a breakpoint on #log only we got a hit and
could confirm the issue this way.
The path is actually some levels deep. All the parent paths don't exist
either so they are created as well. However, no exception is thrown fro
them. The sequence is as follows.
The only difference is that all paths up to including l5 do not actually
have any data. Only l6 has some data. Could there be some latency issues?
For completeness, the embedded server is started as follows.
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Invalid [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|11h 43m||1||Gunnar Wagenknecht||20/May/11 18:30|