I realize this is discussion is over, but i did want to make one quick
clarification. when we talk about ensembles, we are talking about the
servers that make up the zookeeper service. we refer to the servers that
use the zookeeper service as clients. we have systems here that use
ensembles of
Chubby and Zookeeper have very different ways at getting to similar
purposes. Chubby is a locking service, while zookeeper is all about
avoiding locks. Zookeeper is better described as a coordination service.
Regarding performance, I am pretty sure that Zookeeper could keep up with
some pretty
When I first discovered Zookeeper last year, it was all about the
low-level file-system semantics, and letting the client use it with
several knowns recipes (design patterns, algorithms, etc).
And I remember it mentioning that some people within Yahoo were working
on a nice client-side
Hi Fernando,
Our 3.2 release is focussed more on having such recipes in a clieaner and
reliable way.
One of the jiras that focusses on this is
http://issues.apache.org/jira/browse/ZOOKEEPER-78.
We hope to add more of such recipes in 3.2.
Thanks
mahadev
On 3/6/09 2:30 PM, Fernando Padilla
