[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308034#comment-15308034
]
ASF GitHub Bot commented on STORM-822:
--------------------------------------
Github user hmcl commented on the pull request:
https://github.com/apache/storm/pull/1131
@jianbzhou **Storm** guarantees that all the messages are either acked or
failed. There is the property "topology.message.timeout.secs"
https://github.com/apache/storm/blob/master/storm-core/src/jvm/org/apache/storm/Config.java#L1669
If Storm is configured to use acks, and the acks don't arrive in a certain
amount of time, the tuple will be retired. You don't have to worry about the
scenario you described, and basically implement the timeout yourself.
> Kafka Spout New Consumer API
> ----------------------------
>
> Key: STORM-822
> URL: https://issues.apache.org/jira/browse/STORM-822
> Project: Apache Storm
> Issue Type: Story
> Components: storm-kafka
> Reporter: Thomas Becker
> Assignee: Hugo Louro
> Fix For: 1.0.0, 2.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
