[jira] [Updated] (STORM-511) Storm-Kafka spout keeps sending fetch requests with invalid offset

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

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

Rick Kellogg updated STORM-511:
-------------------------------
    Component/s: storm-kafka

> Storm-Kafka spout keeps sending fetch requests with invalid offset
> ------------------------------------------------------------------
>
>                 Key: STORM-511
>                 URL: https://issues.apache.org/jira/browse/STORM-511
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 0.9.3
>            Reporter: Viktor Taranenko
>            Assignee: Viktor Taranenko
>              Labels: kafka
>             Fix For: 0.9.3, 0.9.3-rc2
>
>
> With default behaviour (KafkaConfig.useStartOffsetTimeIfOffsetOutOfRange == true) when Kafka returns the error about offset being out of range, storm.kafka.KafkaUtils.fetchMessages tries to fix offset in local scope and retry fetch request. But if there are no more messages appeared under that specified partition it will never update the PartitionManager, but keep sending tons of requests with invalid offset to Kafka broker. On both sides Storm and Kafka logs grow extremely quick during that time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)