Almost all my zk agents use asynchronous api; mainly because all services
are intrinsically asynchronous.
In fact I've wrapped the Zookeeper client to hide synchronous methods; so
anyone who want to develop new agents should think asynchronously.
It could be hard at first but one you are used to it, the resulting code is
cleaner than with sync api, and more easy to understand and maintain by
On Thu, Feb 9, 2012 at 10:32 AM, Pierre Louis Aublin <
[EMAIL PROTECTED]> wrote:
> Thank you for your replies.
> On 02/09/2012 12:46 AM, Benjamin Reed wrote:
>> the yahoo services mention use asynchronous operations a lot. during
>> startup and reconfig they would have to modify a bunch of znodes. by
>> shooting off the modifications asynchronously, they were able to
>> drastically reduce the startup and reconfig time.
> On 02/09/2012 12:48 AM, Jordan Zimmerman wrote:
>> Some of the Curator recipes use async. For instance, adding a entry into
>> the DistributedQueue is done in the background as there's no reason for
>> the foreground process to wait for this.
>> On 2/8/12 2:09 PM, "Pierre Louis Aublin"<pierre-louis.aublin@**inria.fr<[EMAIL PROTECTED]>
> On Wed, Feb 8, 2012 at 2:09 PM, Pierre Louis Aublin
>> <[EMAIL PROTECTED]> wrote:
>>> Hello everybody
>>> I would like to know if the asynchronous operations of the client API are
>>> often used in applications that use Zookeeper.
>>> In  I found 3 applications built on Zookeeper (the Yahoo! Fetching
>>> Service, Katta and the Yahoo! Message Broker). However, I do not find if
>>> they use the synchronous or asynchronous operations.
>>> The big question I am trying to answer is : is it relevant to consider a
>>> closed-loop model in order to benchmark replicated services (Zookeeper
>>> a good candidate to build replicated services)? Can you give me any clue
>>> Thanks in advance
>>> Pierre Louis Aublin
>>>  ZooKeeper: Wait-free Coordination for Internet-scale Systems, Patrick
>>> Hunt and Mahadev Konar, /Yahoo! Grid;/ Flavio P. Junqueira and Benjamin
>>> Reed, /Yahoo! Research/