[
https://issues.apache.org/jira/browse/KAFKA-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253786#comment-14253786
]
Joe Stein commented on KAFKA-1806:
----------------------------------
I am not sure if this is directly related but perhaps in some way possibly so I
wanted to bring it up. I just created
https://issues.apache.org/jira/browse/KAFKA-1825 which is a case where the
Sarama client is putting Kafka in a bad state. I suspect this might be the
same type of scenario too.
[~lokeshbirla] is there some chance of getting code to reproduce your issue
succinctly (please see my KAFKA-1825 sample code to reproduce and even a binary
for folks to try out).
<< sometimes this issue goes away however I see other problem of leadership
changes very often even when all brokers are running.
This is a another issue I see in production with the Sarama client. I am
working on hunting down the root cause but right now the thinking is that it is
related to https://issues.apache.org/jira/browse/KAFKA-766 and
https://github.com/Shopify/sarama/issues/236 with
https://github.com/Shopify/sarama/commit/03ad601663634fd75eb357fee6782653f5a9a5ed
being a fix for it.
> broker can still expose uncommitted data to a consumer
> ------------------------------------------------------
>
> 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)
