[
https://issues.apache.org/jira/browse/STORM-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186999#comment-15186999
]
ASF GitHub Bot commented on STORM-1608:
---------------------------------------
Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/1190#issuecomment-194268412
@revans2 @ptgoetz I have refactored the code and removed the auto
anchoring/acking for both stateful and non-stateful bolts in a stateful
topology. Currently state checkpointing provides at least once processing and
we could consider providing a best effort checkpointing and relax the
acking/anchoring requirements as a separate feature.
We expect IStatefulBolt implementations also to ack/anchor now and hence
passing OuputCollector in the stateful bolt's prepare method should be fine.
> 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)
