Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # user >> use cases for asynchronous API


Copy link to this message
-
Re: use cases for asynchronous API
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" <[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 [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/
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB