Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/1693
@roshannaik
>1- Retry worthy Errors
Right now theres no explicit `fail` api. When a stage in the stream
completes processing (and possibly emits results), the underlying tuples are
acked automatically. The only way spout will re-emit is after the message
timeout. It may be good to have a fail fast api, but I am not sure how it would
help since the replayed tuple could fail again in processing. Instead the
processing logic itself can have some retry logic (say retry 3 times) and
forward to an error stream and ack the tuple.
> 2- Not worth retrying
This can be handled via branch logic. E.g. send valid values to stream1 and
bad values to stream2.
I have opened https://issues.apache.org/jira/browse/STORM-2282 to discuss
ideas around this and see what apis can be added.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
