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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
