You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "lokesh Birla (JIRA)" <ji...@apache.org> on 2014/12/22 20:46:13 UTC

[jira] [Commented] (KAFKA-1806) broker fetch request uses old leader offset which is higher than current leader offset causes error

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

lokesh Birla commented on KAFKA-1806:
-------------------------------------

Neha,

Could you please update on this? With my recent comment and title change for the problem you should now know the detail information about the problem. Please let me know if you need further information. 

Lokesh

> broker fetch request uses old leader offset which is higher than current leader offset causes error
> ---------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-1806
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1806
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 0.8.1.1
>            Reporter: lokesh Birla
>            Assignee: Neha Narkhede
>
> Although following issue: https://issues.apache.org/jira/browse/KAFKA-727
> is marked fixed but I still see this issue in 0.8.1.1. I am able to reproducer the issue consistently. 
> [2014-08-18 06:43:58,356] ERROR [KafkaApi-1] Error when processing fetch request for partition [mmetopic4,2] offset 1940029 from consumer with correlation id 21 (kafka.server.Kaf
> kaApis)
> java.lang.IllegalArgumentException: Attempt to read with a maximum offset (1818353) less than the start offset (1940029).
>         at kafka.log.LogSegment.read(LogSegment.scala:136)
>         at kafka.log.Log.read(Log.scala:386)
>         at kafka.server.KafkaApis.kafka$server$KafkaApis$$readMessageSet(KafkaApis.scala:530)
>         at kafka.server.KafkaApis$$anonfun$kafka$server$KafkaApis$$readMessageSets$1.apply(KafkaApis.scala:476)
>         at kafka.server.KafkaApis$$anonfun$kafka$server$KafkaApis$$readMessageSets$1.apply(KafkaApis.scala:471)
>         at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:233)
>         at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:233)
>         at scala.collection.immutable.Map$Map1.foreach(Map.scala:119)
>         at scala.collection.TraversableLike$class.map(TraversableLike.scala:233)
>         at scala.collection.immutable.Map$Map1.map(Map.scala:107)
>         at kafka.server.KafkaApis.kafka$server$KafkaApis$$readMessageSets(KafkaApis.scala:471)
>         at kafka.server.KafkaApis$FetchRequestPurgatory.expire(KafkaApis.scala:783)
>         at kafka.server.KafkaApis$FetchRequestPurgatory.expire(KafkaApis.scala:765)
>         at kafka.server.RequestPurgatory$ExpiredRequestReaper.run(RequestPurgatory.scala:216)
>         at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)