[jira] [Resolved] (KAFKA-2219) reassign partition fails with offset 0 being asked for but obviously not there

["Manikumar (JIRA)" <ji...@apache.org>]

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

Manikumar resolved KAFKA-2219.
------------------------------
    Resolution: Auto Closed

Closing inactive issue.  Please reopen if the issue still exists in newer versions.

> reassign partition fails with offset 0 being asked for but obviously not there
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-2219
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2219
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.1.1
>            Reporter: Joe Stein
>            Priority: Critical
>
> may be related to there being no data anymore in the partition
> [2015-05-23 15:51:05,506]  122615762 [request-expiration-task] ERROR kafka.server.KafkaApis  - [KafkaApi-10206101] Error when processing fetch request for partition [cs.sensor.wrapped,44] offset 0 from fo
> llower with correlation id 3
> kafka.common.OffsetOutOfRangeException: Request for offset 0 but we only have log segments in the range 1339916216 to 1339916216.
>         at kafka.log.Log.read(Log.scala:380)
>         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:244)
>         at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>         at scala.collection.immutable.Map$Map2.foreach(Map.scala:130)
>         at scala.collection.TraversableLike$class.map(TraversableLike.scala:244)
>         at scala.collection.AbstractTraversable.map(Traversable.scala:105)
>         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:722)
> This topic was stopped from having data produced to it, wait for the log clean up (so no data in partitions) and then reassign. it also maybe related to some brokers being an bad state



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)