That's a good question. Off the top of my head I don't remember any
fundamentally good reason why we don't allow it - apart from:
- broker registration paths are ephemeral so topic creation cannot
succeed when there are insufficient brokers available
- it may be confusing to some users to successfully create a topic and
allow its partition replicas to be assigned to brokers that are

One can possibly argue that topic creation should not be permitted
with _any_ unavailable brokers since extended unavailability could
result in imbalanced partition distribution (when the unavailable
brokers are restored).

Anyway, unless I'm missing something obvious I think your point is
worth discussing further in a jira.


On Tue, Oct 15, 2013 at 1:47 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