[jira] [Assigned] (STORM-1455) kafka spout should not reset to the beginning of partition when offsetoutofrange exception occurs

["Jungtaek Lim (JIRA)" <ji...@apache.org>]

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

Jungtaek Lim reassigned STORM-1455:
-----------------------------------

    Assignee: Abhishek Agarwal  (was: Jungtaek Lim)

> kafka spout should not reset to the beginning of partition when offsetoutofrange exception occurs
> -------------------------------------------------------------------------------------------------
>
>                 Key: STORM-1455
>                 URL: https://issues.apache.org/jira/browse/STORM-1455
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 1.0.0
>            Reporter: Abhishek Agarwal
>            Assignee: Abhishek Agarwal
>
> https://github.com/apache/storm/blob/master/external/storm-kafka/src/jvm/storm/kafka/PartitionManager.java#L190
> {noformat}
> try {
>             msgs = KafkaUtils.fetchMessages(_spoutConfig, _consumer, _partition, offset);
>         } catch (TopicOffsetOutOfRangeException e) {
>             _emittedToOffset = KafkaUtils.getOffset(_consumer, _partition.topic, _partition.partition, kafka.api.OffsetRequest.EarliestTime());
>             LOG.warn("{} Using new offset: {}", _partition.partition, _emittedToOffset);
> {noformat}
> If there was one old offset out of range, partition manager will re-send all the offsets from EarliestTime to _emittedOffset. 



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