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 Plain View
Kafka >> mail # dev >> [jira] [Resolved] (KAFKA-861) IndexOutOfBoundsException while fetching data from leader


Copy link to this message
-
[jira] [Resolved] (KAFKA-861) IndexOutOfBoundsException while fetching data from leader

     [ https://issues.apache.org/jira/browse/KAFKA-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao resolved KAFKA-861.
---------------------------

    Resolution: Fixed

Thanks for patch v2. We should do "size < Message.MinHeaderSize" instead of "size <= Message.MinHeaderSize" in ByteBufferMessagesSet since it's possible to have a valid message whose size is exactly Message.MinHeaderSize. Committed to 0.8 with the change.

Great investigation.
                
> IndexOutOfBoundsException while fetching data from leader
> ---------------------------------------------------------
>
>                 Key: KAFKA-861
>                 URL: https://issues.apache.org/jira/browse/KAFKA-861
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Sriram Subramanian
>            Assignee: Sriram Subramanian
>             Fix For: 0.8
>
>         Attachments: KAFKA-861.patch, KAFKA-861-v2.patch
>
>
> 2013-04-09 16:36:50,051] ERROR [ReplicaFetcherThread-0-261], Error due to  (kafka.server.ReplicaFetcherThread)
> kafka.common.KafkaException: error processing data for topic firehoseUpdates partititon 14 offset 53531364
>         at kafka.server.AbstractFetcherThread$$anonfun$processFetchRequest$4.apply(AbstractFetcherThread.scala:136)
>         at kafka.server.AbstractFetcherThread$$anonfun$processFetchRequest$4.apply(AbstractFetcherThread.scala:113)
>         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.processFetchRequest(AbstractFetcherThread.scala:113)
>         at kafka.server.AbstractFetcherThread.doWork(AbstractFetcherThread.scala:89)
>         at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
> Caused by: java.lang.IndexOutOfBoundsException
>         at java.nio.Buffer.checkIndex(Buffer.java:512)
>         at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:121)
>         at kafka.message.Message.compressionCodec(Message.scala:202)
>         at kafka.message.ByteBufferMessageSet$$anon$1.makeNextOuter(ByteBufferMessageSet.scala:174)
>         at kafka.message.ByteBufferMessageSet$$anon$1.makeNext(ByteBufferMessageSet.scala:197)
>         at kafka.message.ByteBufferMessageSet$$anon$1.makeNext(ByteBufferMessageSet.scala:145)
>         at kafka.utils.IteratorTemplate.maybeComputeNext(IteratorTemplate.scala:61)
>         at kafka.utils.IteratorTemplate.hasNext(IteratorTemplate.scala:53)
>         at scala.collection.IterableLike$class.isEmpty(IterableLike.scala:92)
>         at kafka.message.MessageSet.isEmpty(MessageSet.scala:67)
>         at scala.collection.TraversableLike$class.lastOption(TraversableLike.scala:512)
>         at kafka.message.MessageSet.lastOption(MessageSet.scala:67)

--
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

 
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