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 >> Proper use of ConsumerConnector


Copy link to this message
-
Re: Proper use of ConsumerConnector
It tracks the consumed offset, not the fetched offset.

Thanks,

Jun

On Fri, Dec 21, 2012 at 9:46 AM, Tom Brown <[EMAIL PROTECTED]> wrote:

> Does the ConsumerConnector keep track of the offsets of data
> downloaded from the server (and queued for consumption by the end user
> of the API), or does it keep track of the actual offset that has been
> consumed by the end user?
>
> --Tom
>
> On Fri, Dec 21, 2012 at 10:37 AM, Neha Narkhede <[EMAIL PROTECTED]>
> wrote:
> >>  But if crash happens just after offset committed, then unprocessed
> >> message in consumer will be skipped after reconnected.
> >>
> >
> > If the consumer crashes, you will get duplicates, not lose any data.
> >
> > Thanks,
> > Neha
>

 
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