Jimmy,
I am not very familiar with the python java client, you may directly ask
its author:
https://cwiki.apache.org/confluence/display/KAFKA/Clients
On Thu, Nov 6, 2014 at 7:57 AM, Jimmy John wrote:
> I dug deeper and saw this during normal operation:
>
> In the kafka broker log:
>
> [2014-11
I dug deeper and saw this during normal operation:
In the kafka broker log:
[2014-11-03 21:39:25,658] ERROR [KafkaApi-8] Error when processing fetch
request for partition [activity.stream,5] offset 7475239 from consumer with
correlation id 69 (kafka.server.KafkaApis)
kafka.common.OffsetOutOfRange
I dug deeper and saw this during normal operation:
In the kafka broker log:
[2014-11-03 21:39:25,658] ERROR [KafkaApi-8] Error when processing fetch
request for partition [activity.stream,5] offset 7475239 from consumer with
correlation id 69 (kafka.server.KafkaApis)
kafka.common.OffsetOutOfRange
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 wrote:
> Hi Jim,
>
> OffsetOutOfRange means that the partition's log of
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 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.
