Hi Gustavo,
I have a very strong feeling against more complex operations in the ZK server.
These are things that should be provided by a ZK client helper library. The
zkclient library from 101tec for example gives you exactly that.
If you're planning to write another layer on top of the ZK API
My own opinion is that lots of these structure sorts of problems are solved
by putting the structure into a single znode. Atomic creation and update
come for free at that point and we can even make the node ephemeral which we
can't really do if there are children.
Sure, it makes sense that
Hi Thomas,
I have a very strong feeling against more complex operations in the ZK server.
Can you please describe a little better what that feeling is about?
These are things that should be provided by a ZK client helper library. The
Which things should be provided by client helper
Gustavo Niemeyer:
Hi Thomas,
I have a very strong feeling against more complex operations in the ZK
server.
Can you please describe a little better what that feeling is about?
Every functionality added to ZK will make it harder to maintain. The use case
you're asking for is IMHO easily
Todd Nine:
[...]
UC1: Synchronized Jobs
1. A job is fired across all nodes
2. The nodes wait until the barrier is entered by all participants
3. The nodes process the data and leave
4. On all nodes leaving the barrier, the Leader node marks the job as
complete.
UC2: Multiple Jobs per
Hi,
I am using the Zookeeper Java client class from Scala for some synchronous
communication (no watches, no async). Fairly simple. Every now and then my
application needs to use ZK and then creates a client, does its thing, and
closes the client.
What happens though is that I keep having
