zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Louis Aublin <pierre-louis.aub...@inria.fr>
Subject Re: use cases for asynchronous API
Date Thu, 09 Feb 2012 09:32:44 GMT
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.
> ben

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.
> -JZ
> On 2/8/12 2:09 PM, "Pierre Louis Aublin"<pierre-louis.aublin@inria.fr>
> wrote:

> On Wed, Feb 8, 2012 at 2:09 PM, Pierre Louis Aublin
> <pierre-louis.aublin@inria.fr>  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 [1] 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
>> that?
>> Thanks in advance
>> Pierre Louis Aublin
>> [1] ZooKeeper: Wait-free Coordination for Internet-scale Systems, Patrick
>> Hunt and Mahadev Konar, /Yahoo! Grid;/ Flavio P. Junqueira and Benjamin
>> Reed, /Yahoo! Research/

View raw message