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 >> Question about watcher guarantees


Copy link to this message
-
Re: Question about watcher guarantees
On Wed, Mar 14, 2012 at 12:50 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote:

> > This means there's not really any way to avoid the "flood" of client
> get-state requests (getData/getChildren/exists) that will happen when a
> change triggers a watcher. In your example a getData call will happen in
> every client at step (2) whenever a change happens. There's no way to avoid
> it. I'm Ok with that, it's just that the documentation (at some place I
> cant seem to find now) says to try to avoid this.
>
> See the recipes page for some examples of how to avoid herd effects.
> Sometimes it's possible, but not always:
> http://zookeeper.apache.org/doc/trunk/recipes.html
I would add that sometimes it is important, but not always.
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