You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "sriram (JIRA)" <ji...@apache.org> on 2014/06/13 18:05:03 UTC

[jira] [Commented] (KAFKA-1492) Getting error when sending producer request at the broker end with a single broker

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

sriram commented on KAFKA-1492:
-------------------------------

When running consumer.

Broker Console:
[2014-06-13 11:03:43,075] WARN [KafkaApi-1] Offset request with correlation id 0 from client console-consumer-28645-ConsumerFetcherThread-console-consumer-28645_TXCDTL0249057V-1402675420035-8dbe6843-0-1 on partition [samsung,0] failed due to Leader not local for partition [samsung,0] on broker 1 (kafka.server.KafkaApis)
[2014-06-13 11:03:43,109] INFO Closing socket connection to /135.70.254.3. (kafka.network.Processor)



Client Console:

2014-06-13 11:03:43,078] WARN [console-consumer-28645_TXCDTL0249057V-1402675420035-8dbe6843-leader-finder-thread], Failed to add leader for partition [samsung,0]; will retry (kafka.consumer.ConsumerFetcherManager$LeaderFinderThread)
afka.common.NotLeaderForPartitionException
       at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
       at java.lang.Class.newInstance(Class.java:374)
       at kafka.common.ErrorMapping$.exceptionFor(ErrorMapping.scala:70)
       at kafka.consumer.SimpleConsumer.earliestOrLatestOffset(SimpleConsumer.scala:147)
       at kafka.consumer.ConsumerFetcherThread.handleOffsetOutOfRange(ConsumerFetcherThread.scala:60)
       at kafka.server.AbstractFetcherThread.addPartition(AbstractFetcherThread.scala:175)
       at kafka.server.AbstractFetcherManager.addFetcher(AbstractFetcherManager.scala:80)
       at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$7.apply(ConsumerFetcherManager.scala:97)
       at kafka.consumer.ConsumerFetcherManager$LeaderFinderThread$$anonfun$doWork$7.apply(ConsumerFetcherManager.scala:93)
       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)

> Getting error when sending producer request at the broker end with a single broker
> ----------------------------------------------------------------------------------
>
>                 Key: KAFKA-1492
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1492
>             Project: Kafka
>          Issue Type: Bug
>          Components: producer 
>    Affects Versions: 0.8.1.1
>            Reporter: sriram
>            Assignee: Jun Rao
>
> Tried to run a simple example by sending a message to a single broker . Getting error 
> [2014-06-13 08:35:45,402] INFO Closing socket connection to /127.0.0.1. (kafka.network.Processor)
> [2014-06-13 08:35:45,440] WARN [KafkaApi-1] Produce request with correlation id 2 from client  on partition [samsung,0] failed due to Leader not local for partition [samsung,0] on broker 1 (kafka.server.KafkaApis)
> [2014-06-13 08:35:45,440] INFO [KafkaApi-1] Send the close connection response due to error handling produce request [clientId = , correlationId = 2, topicAndPartition = [samsung,0]] with Ack=0 (kafka.server.KafkaApis)
> OS- Windows 7 , JDK 1.7 , Scala 2.10



--
This message was sent by Atlassian JIRA
(v6.2#6252)