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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.8.1.1
• Fix Version/s: 0.8.2.0
• Component/s: consumer
• Assignee: Neha Narkhede
• Reporter: lokesh Birla
• Created: 04/Dec/14 22:16
• Updated: 24/Dec/14 01:06
• Resolved: 24/Dec/14 01:06

Description

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)