You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Viktor Taranenko (JIRA)" <ji...@apache.org> on 2014/09/27 16:19:33 UTC
[jira] [Created] (STORM-511) Storm-Kafka spout keeps sending fetch
requests with invalid offset
Viktor Taranenko created STORM-511:
--------------------------------------
Summary: 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
Affects Versions: 0.9.3-incubating
Reporter: Viktor Taranenko
Fix For: 0.9.3-incubating
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)