You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "P. Taylor Goetz (JIRA)" <ji...@apache.org> on 2017/02/08 20:54:41 UTC

[jira] [Resolved] (STORM-2270) Kafka spout should consume from latest when zk committed offset bigger than latest offset

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

P. Taylor Goetz resolved STORM-2270.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0

Merged to 1.x-branch.

> Kafka spout should consume from latest when zk committed offset bigger than latest offset
> -----------------------------------------------------------------------------------------
>
>                 Key: STORM-2270
>                 URL: https://issues.apache.org/jira/browse/STORM-2270
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 1.0.0, 0.9.6
>            Reporter: Yuzhao Chen
>              Labels: easyfix
>             Fix For: 1.1.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> Kafka spout should consume from latest when ZK offset bigger than latest offset[ an TopicOffsetOutOfRangeException thrown out ], especially when Kafka topic change it's leader and some data lost, if we consume from earliest offset, much meaningless duplicate records will be re-consumed. So, we should consume from latest offset instead.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)