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

Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2017/07/03 15:05:00 UTC

[jira] [Updated] (STORM-2413) New Kafka spout is ignoring retry limit

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

Jungtaek Lim updated STORM-2413:
--------------------------------
    Fix Version/s: 1.2.0

> New Kafka spout is ignoring retry limit
> ---------------------------------------
>
>                 Key: STORM-2413
>                 URL: https://issues.apache.org/jira/browse/STORM-2413
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka-client
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Critical
>             Fix For: 2.0.0, 1.1.1, 1.2.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The new Kafka spout ignores retry limits. The problem is that a new KafkaSpoutMessageId is constructed on every retry, so the numFails counter it contains is always either 0 or 1. We should reuse the existing message id when retrying a record.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)