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 >> why was auto.offset.reset default changed (so late in the game)?


Copy link to this message
-
Re: why was auto.offset.reset default changed (so late in the game)?
Hi, Jason,

The reasons for this change are: (1) This is probably the most convenient
setting for people to migrate from 0.7 to 0.8. The process is to build an
0.8 shadow cluster using our migration tool, upgrade all consumers to 0.8,
and finally upgrade all producers to 0.8. Since most consumers are likely
real time, when moving from 0.7 to 0.8, it's better for them to pick up the
latest offset in 0.8 so that they don't get too many duplicates (there
could be a small number of message loss for those consumers). (2) This
matches the default behavior of console consumer which is the first thing
that most new users experience. Does that make sense?

Thanks,

Jun
On Tue, Jun 18, 2013 at 9:02 AM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
 
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