replication factor is 1 and there is a broker failure, we can still route
the message, (2) if a bunch of producers are started at the same time, this
prevents them from picking up the same partition in a synchronized way.

You raised a good point, Jun. Regarding #1, shouldn't round robin mean
"round robin to the next available partition", by default?
Regarding #2, this is not a problem since each producer will shuffle the
list of brokers once on startup and then round robin, no?
On Mon, Feb 3, 2014 at 10:45 AM, Jun Rao <[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