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
Kafka >> mail # user >> ways to exit the blocking iterator


Copy link to this message
-
Re: ways to exit the blocking iterator
Neha
Thanks. I am looking for the semantics of ensuring that ALL consumers would
somehow unblock. This is probably not doable with the queue semantics.

/***********************
sent from my android...please pardon occasional typos as I respond @ the
speed of thought
************************/

On Feb 28, 2012 12:44 PM, "Neha Narkhede" <[EMAIL PROTECTED]> wrote:

>> should ideally deliver a unblock message to the iterator and then
continue
delivering the messag...
I'm not sure what you mean by this. What will happen, in your example,
is that the consumer iterator will get messages 1 and 2 only.
If you have multiple instances of the zookeeper consumer, they will
get messages 3 and 4. If you don't, then you will get 3 and 4, the
next time you start the consumer connector again.

Thanks,
Neha
On Tue, Feb 28, 2012 at 6:08 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
> Milind, if you are using t...
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