Please read the Kafka design paper <>.

It may look a little long, but it's as short as it can be. Kafka differs
from other messaging system in a couple of ways, and it's important to
understand the fundamental design choices that were made in order to
understand the way Kafka works.

I believe my previous email already answers both your offset tracking and
retention questions, but if my explanation are not clear enough, then the
next best thing is probably to read the design paper :)

On Tue, Jan 15, 2013 at 12:01 PM, navneet sharma <
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