You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/11/26 23:05:11 UTC

[jira] [Reopened] (STORM-646) KafkaUtils repeat fetch messages which offset is out of range

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

Jungtaek Lim reopened STORM-646:
--------------------------------

Reopening to pick proper resolution.

> KafkaUtils repeat fetch messages which offset is out of range
> -------------------------------------------------------------
>
>                 Key: STORM-646
>                 URL: https://issues.apache.org/jira/browse/STORM-646
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 0.9.2-incubating, 0.9.3
>            Reporter: Xin Wang
>            Assignee: Xin Wang
>
> KafkaUtils repeat fetch messages which offset is out of range.
> This happened when failed list(SortedSet<Long> failed) is not empty and some offset in it is OutOfRange.
> [FIX]
> storm.kafka.PartitionManager.fill():
> ...
> try {
> 	msgs = KafkaUtils.fetchMessages(_spoutConfig, _consumer, _partition, offset);
> } catch (UpdateOffsetException e) {
> 	 _emittedToOffset = KafkaUtils.getOffset(_consumer, _spoutConfig.topic, _partition.partition, _spoutConfig);
> 	LOG.warn("Using new offset: {}", _emittedToOffset);
> 	// fetch failed, so don't update the metrics
> 	//fix bug: remove this offset from failed list when it is OutOfRange
> 	if (had_failed) {
> 		failed.remove(offset);
> 	}
>             return;
> }
> ...



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