Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka, mail # user - Re: no partition leader yet for partition 0 (0.8.0)


Copy link to this message
-
Re: no partition leader yet for partition 0 (0.8.0)
Jun Rao 2013-03-06, 15:52
num.partitions is used when topics are auto-created by the brokers, not
by CreateTopicCommand.

Thanks,

Jun

On Wed, Mar 6, 2013 at 5:47 AM, Chris Curtin <[EMAIL PROTECTED]> wrote:

> Hi,
>
> 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?
>
> Thanks,
>
> Chris
>
>
> On Mon, Mar 4, 2013 at 2:21 PM, Chris Curtin <[EMAIL PROTECTED]>
> wrote:
>
> > I was able to reproduce today after upgrading to HEAD (as of 3/4/2013)
> >
> > JIRA:
> >
> > https://issues.apache.org/jira/browse/KAFKA-784
> >
> >
> >
> > On Mon, Dec 3, 2012 at 11:09 AM, Chris Curtin <[EMAIL PROTECTED]
> >wrote:
> >
> >> Hi Jun,
> >>
> >> Couldn't make either happen again with a clean start (removed all Kafka
> >> and Zookeeper configuration and data files).
> >>
> >> Thanks,
> >>
> >> Chris
> >>
> >>
> >>
> >>>
> >>
> >
>