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 >> Re: consumer question


Copy link to this message
-
Re: consumer question
Yes, the Kafka team has told me that this is how it works (at least for 0.72).

Philip

On Fri, Aug 23, 2013 at 7:53 AM, Yu, Libo <[EMAIL PROTECTED]> wrote:
> Hi team,
>
> Right now, from a stream, an iterator can be obtained which has a blocking hasNext().
> So what is the implementation behind the iterator? I assume there must be queue and
> the iterator monitors the queue. And a separate thread fetches data and feeds to the
> queue when it is almost empty. If that is the case, no more optimization needs to be
> done by our users. Please confirm if there is a separate thread that fetches data and
> feeds to the queue. Thanks.
>
>
> Regards,
>
> Libo
>

 
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