Home | About | Sematext search-lucene.com search-hadoop.com
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
 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)
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
>
>
> On Wed, Nov 28, 2012 at 12:12 PM, Chris Curtin <[EMAIL PROTECTED]>wrote:
>
>> Hi Jun,
>>
>> Sorry, neither the missing 0 leader or all those WARN messages have
>> been reproducible. Tried several times this morning.
>>
>> I'll be starting from a green-field cluster again this afternoon so I'll
>> keep an eye out for it happening again.
>>
>> Thanks,
>>
>> Chris
>>
>>
>> On Wed, Nov 28, 2012 at 12:08 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
>>
>>> Chris,
>>>
>>> Not sure what happened to the WARN logging that you saw. Is that easily
>>> reproducible? As for log4j, you just need to change log4j.properties. You
>>> can find out on the web how to configure a rolling log file.
>>>
>>> Thanks,
>>>
>>> Jun
>>>
>>> On Wed, Nov 28, 2012 at 5:10 AM, Chris Curtin <[EMAIL PROTECTED]
>>> >wrote:
>>>
>>> > Hi Jun,
>>> >
>>> > No, all 9 brokers are up and when I look at the files in
>>> /opt/kafka-[]-logs
>>> > there is data for partition 0 of that topic on 3 different brokers.
>>> >
>>> > After confirming this was still happening this morning, I bounced all
>>> the
>>> > brokers and on restart one of them took over primary on partition 0. No
>>> > more errors after reboot.
>>> >
>>> > However, I now have a different problem. To see if the issue was
>>> creating a
>>> > new topic with all the brokers live, I created a new topic using the
>>> same
>>> > command line as below. The list_topics show it was created with
>>> primaries
>>> > on all partitions. However on one of machines (with 3 brokers running
>>> (1,2&
>>> > 3) )  I keep getting the following warning:
>>> >
>>> > [2012-11-28 07:56:46,014] WARN [ReplicaFetcherThread-9-0-on-broker-1],
>>> > error for test2 2 to broker 9 (kafka.server.ReplicaFetcherThread)
>>> > kafka.common.UnknownTopicOrPartitionException
>>> >         at
>>> sun.reflect.GeneratedConstructorAccessor1.newInstance(Unknown
>>> > Source)
>>> >         at
>>> >
>>> >
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>> >         at
>>> java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>>> >         at java.lang.Class.newInstance0(Class.java:355)
>>> >         at java.lang.Class.newInstance(Class.java:308)
>>> >         at
>>> kafka.common.ErrorMapping$.exceptionFor(ErrorMapping.scala:70)
>>> >         at
>>> >
>>> >
>>> kafka.server.AbstractFetcherThread$$anonfun$doWork$5$$anonfun$apply$3.apply(AbstractFetcherThread.scala:131)
>>> >         at
>>> >
>>> >
>>> kafka.server.AbstractFetcherThread$$anonfun$doWork$5$$anonfun$apply$3.apply(AbstractFetcherThread.scala:131)
>>> >         at kafka.utils.Logging$class.warn(Logging.scala:88)
>>> >         at
>>> kafka.utils.ShutdownableThread.warn(ShutdownableThread.scala:23)
>>> >         at
>>> >
>>> >
>>> kafka.server.AbstractFetcherThread$$anonfun$doWork$5.apply(AbstractFetcherThread.scala:130)
>>> >         at
>>> >
>>> >
>>> kafka.server.AbstractFetcherThread$$anonfun$doWork$5.apply(AbstractFetcherThread.scala:106)
>>> >         at scala.collection.immutable.Map$Map2.foreach(Map.scala:127)
>>> >         at
>>> >
>>> kafka.server.AbstractFetcherThread.doWork(AbstractFetcherThread.scala:106)
>>> >         at
>>> kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:50)
>>> > [2012-11-28 07:56:46,289] WARN [ReplicaFetcherThread-8-0-on-broker-1],
>>> > error for test2 1 to broker 8 (kafka.server.ReplicaFetcherThread)
>>> > kafka.common.UnknownTopicOrPartitionException
>>> >         at
>>> sun.reflect.GeneratedConstructorAccessor1.newInstance(Unknown
>>> > Source)
>>> >         at
>>> >
>>> >
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

 
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