[
https://issues.apache.org/jira/browse/STORM-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184437#comment-15184437
]
ASF GitHub Bot commented on STORM-1608:
---------------------------------------
Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/1190#issuecomment-193616307
@revans2 anchoring/acking in enforced for stateful & non-stateful bolts in
a stateful topology to provide at-least once guarantee for the state updates.
For the stateful bolts, the tuples that were part of the last state update are
automatically acked after that state update is committed. Non-stateful bolts
need to either extend the BaseBasicBolt or do the acking themselves.
The state checkpointing mechanism and the guarantee is documented
[here](https://github.com/apache/storm/blob/asf-site/documentation/State-checkpointing.mdl).
This does not explicitly mention whether the bolt is expected to ack or not. I
can add that to the doc and the javadocs.
> Fix stateful topology acking behavior
> -------------------------------------
>
> Key: STORM-1608
> URL: https://issues.apache.org/jira/browse/STORM-1608
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 1.0.0, 2.0.0
> Reporter: Arun Mahadevan
> Assignee: Arun Mahadevan
>
> Right now the acking is automatically taken care of for the non-stateful
> bolts in a stateful topology. This leads to double acking if BaseRichBolts
> are part of the topology. For the non-stateful bolts, its better to let the
> bolt do the acking rather than automatically acking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
