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 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 being
> a good candidate to build replicated services)? Can you give me any clue on
> 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/