Chris Riccomini created KAFKA-627:
-------------------------------------

             Summary: Make UnknownTopicOrPartitionException a WARN in broker
                 Key: KAFKA-627
                 URL: https://issues.apache.org/jira/browse/KAFKA-627
             Project: Kafka
          Issue Type: Bug
          Components: core
    Affects Versions: 0.8
         Environment: Kafka 0.8, RHEL6, Java 1.6
            Reporter: Chris Riccomini


Currently, when sending messages to a topic that doesn't yet exist, the broker 
spews out these "errors" as it tries to auto-create new topics. I spoke with 
Neha, and she said that this should be a warning, not an error.

Could you please change it to something less scary, if, in fact, it's not scary.

2012/11/14 22:38:53.238 INFO [LogManager] [kafka-request-handler-6] [kafka] []  
[Log Manager on Broker 464] Created log for 'firehoseReads'-5
2012/11/14 22:38:53.241 WARN [HighwaterMarkCheckpoint] 
[kafka-request-handler-6] [kafka] []  No previously checkpointed highwatermark 
value found for topic firehoseReads partition 5. Returning 0 as the 
highwatermark
2012/11/14 22:38:53.242 INFO [Log] [kafka-request-handler-6] [kafka] []  [Kafka 
Log on Broker 464], Truncated log segment 
/export/content/kafka/i001_caches/firehoseReads-5/00000000000000000000.log to 
target offset 0
2012/11/14 22:38:53.242 INFO [ReplicaFetcherManager] [kafka-request-handler-6] 
[kafka] []  [ReplicaFetcherManager on broker 464] adding fetcher on topic 
firehoseReads, partion 5, initOffset 0 to broker 466 with fetcherId 0
2012/11/14 22:38:53.248 ERROR [ReplicaFetcherThread] 
[ReplicaFetcherThread-466-0-on-broker-464] [kafka] []  
[ReplicaFetcherThread-466-0-on-broker-464], error for firehoseReads 5 to broker 
466
kafka.common.UnknownTopicOrPartitionException
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        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:68)
        at 
kafka.server.AbstractFetcherThread$$anonfun$doWork$5$$anonfun$apply$3.apply(AbstractFetcherThread.scala:124)
        at 
kafka.server.AbstractFetcherThread$$anonfun$doWork$5$$anonfun$apply$3.apply(AbstractFetcherThread.scala:124)
        at kafka.utils.Logging$class.error(Logging.scala:102)
        at kafka.utils.ShutdownableThread.error(ShutdownableThread.scala:23)
        at 
kafka.server.AbstractFetcherThread$$anonfun$doWork$5.apply(AbstractFetcherThread.scala:123)
        at 
kafka.server.AbstractFetcherThread$$anonfun$doWork$5.apply(AbstractFetcherThread.scala:99)
        at 
scala.collection.immutable.HashMap$HashMap1.foreach(HashMap.scala:125)
        at 
scala.collection.immutable.HashMap$HashTrieMap.foreach(HashMap.scala:344)
        at 
scala.collection.immutable.HashMap$HashTrieMap.foreach(HashMap.scala:344)
        at 
kafka.server.AbstractFetcherThread.doWork(AbstractFetcherThread.scala:99)
        at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:50)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to