[jira] [Commented] (KAFKA-877) Still getting kafka.common.NotLeaderForPartitionException

["Robert P. Thille (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016619#comment-16016619 ] 

Robert P. Thille commented on KAFKA-877:
----------------------------------------

We see this in Kafka 0.8.2.1 when our systems get overloaded and either ZooKeeper gets stalled trying to fsync, or Kafka gets starved and loses its connection to ZK.  It takes a restart of the brokers to get them properly in sync thereafter.

> Still getting kafka.common.NotLeaderForPartitionException
> ---------------------------------------------------------
>
>                 Key: KAFKA-877
>                 URL: https://issues.apache.org/jira/browse/KAFKA-877
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>         Environment: DEV
>            Reporter: BalajiSeshadri
>            Priority: Blocker
>         Attachments: KAFKA-816.jpg
>
>
> Using the below trunk and i still see error happening.Please let us know if this can be fixed.
> https://github.com/apache/kafka.git
> [2013-04-25 16:47:08,924] WARN [console-consumer-24019_MERD7-21964-1366930009136-8b7f9eb7-leader-finder-thread], Failed to add fetcher for [mytopic,0] to broker id:0,host:MERD7-21964.echostar.com,port:9092 (kafka.consumer.ConsumerFetcherManager$$anon$1)
> kafka.common.NotLeaderForPartitionException
>         at sun.reflect.GeneratedConstructorAccessor1.newInstance(Unknown Source)
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
>         at java.lang.Class.newInstance0(Class.java:372)
>         at java.lang.Class.newInstance(Class.java:325)
>         at kafka.common.ErrorMapping$.exceptionFor(ErrorMapping.scala:72)
>         at kafka.consumer.SimpleConsumer.earliestOrLatestOffset(SimpleConsumer.scala:163)
>         at kafka.consumer.ConsumerFetcherThread.handleOffsetOutOfRange(ConsumerFetcherThread.scala:61)
>         at kafka.server.AbstractFetcherThread.addPartition(AbstractFetcherThread.scala:167)
>         at kafka.server.AbstractFetcherManager.addFetcher(AbstractFetcherManager.scala:48)
>         at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:79)
>         at kafka.consumer.ConsumerFetcherManager$$anon$1$$anonfun$doWork$3.apply(ConsumerFetcherManager.scala:75)
>         at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95)
>         at scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:95)
>         at scala.collection.Iterator$class.foreach(Iterator.scala:772)
>         at scala.collection.mutable.HashTable$$anon$1.foreach(HashTable.scala:157)
>         at scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:190)
>         at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:45)
>         at scala.collection.mutable.HashMap.foreach(HashMap.scala:95)
>         at kafka.consumer.ConsumerFetcherManager$$anon$1.doWork(ConsumerFetcherManager.scala:75)
>         at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
> We are evaluating Kafka for our new messaging system and we had tough time running in windows.
> We somehow managed to run 0.8 using cygwin but when we run the console producer/consumer,we are not getting messages from consumer.
> Please help us to fix this issue,this might not be related but its keeping on throwing this error on consumer side. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)