This is a bit of a flaw in the topic metadata request logic on the broker
at startup. We need to fix it. Before a broker receives the first
LeaderAndIsrRequest/UpdateMetadataRequest, it is technically not ready to
start serving any request. But it still ends up serving
TopicMetadataRequest which can re-create topics accidentally. It shouldn't
succeed, but this is still a problem. Could you file a JIRA?

On Thu, Oct 31, 2013 at 8:41 PM, 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