Hi Jim, Maybe your consumer lagged behind the current smallest offset. And why it happened? you might take a look at this ticket https://issues.apache.org/jira/browse/KAFKA-1640
On Wed, Nov 5, 2014 at 8:46 AM, Guozhang Wang <wangg...@gmail.com> wrote: > Hi Jim, > > OffsetOutOfRange means that the partition's log offset range is [a, b] and > the requested offset is either < a or > b. It could be caused by log > truncation based on the retention policy while consumer fetching at the > same time. > > Guozhang > > On Tue, Nov 4, 2014 at 4:21 PM, Jimmy John <jimmyisl...@gmail.com> wrote: > > > Hello, > > > > We are using kafka version 0.8.1 and the python kafka client. > > Everything has been working fine and suddenly this morning I saw > > a OffsetOutOfRange on one of the partitions. (We have 20 partitions in > our > > kafka cluster) > > > > We fixed it by seeking to the head offset and restarting the app. > > > > But why would we get such an error during normal course of operations? > > isn't the offset a continually increasing number? > > > > thx > > Jim > > > > @jimmyislive > > > > > > -- > -- Guozhang > -- have a good day! chenshang'an
