I saw Neha's comment in the JIRA and I understand it.
However, it occurred to me after reading it that there might be a second issue. When I created the topics and didn't define a partition count, it created only one partition. However in my server.properties file I've set 'num.partitions' to 5.
Shouldn't this have caused the new topic to have 5 partitions by default?
A quick look at the code for CreateTopicCommand.scala shows the option being defaulted to 1. If the only way to create topics is via that command, what is the 'num.partitions' used for?
Chris On Mon, Mar 4, 2013 at 2:21 PM, Chris Curtin <[EMAIL PROTECTED]> wrote:
Re: no partition leader yet for partition 0 (0.8.0)
num.partitions is used when topics are auto-created by the brokers, not by CreateTopicCommand.
On Wed, Mar 6, 2013 at 5:47 AM, Chris Curtin <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext