No, you need something to process the acks otherwise there's no way to tell what has processed successfully and what is timing out. It's better to figure out why enabling acking is causing your topology to fail. That sounds ... bad.
On Tue, Mar 17, 2015 at 11:07 AM, hjh <[email protected]> wrote: > Thank you very much for the quick response. By the way I forgot to tell > that I disabled the acker in the topology since the topology may die after > a few seconds if I do not turn off ackers. In this case is it still > possible to do guaranteed message processing for some of the bolts? Thank > you!! > > > On 03/17/2015 10:16 AM, Nathan Leung wrote: > > When you emit from bolt c do not anchor the output tuple to the input > tuple. > On Mar 17, 2015 9:55 AM, "hjh" <[email protected]> wrote: > >> Hi everyone, >> I am confused about reliability API of storm. It seems that >> guaranteed message processing is only for spout. What if I need to >> guarantee message being processed in a subset of bolts? For example, bolt >> A, B, C are connected and tuples are processed from A to B and to C, what >> should I do if I want tuples passed through these three bolts being >> processed fully? I mean once a tuple is passed to A then I should make sure >> that this tuple is processed in B and C but after that I do not care >> whether it is lost or not? Thank you very much!! >> >> Best wishes!! >> >> >
