Ahhh got it!. Thanks a lot. On Tue, 19 Jan 2016 at 12:23 John Yost <[email protected]> wrote:
> Close. :) The tuples that failed to process in the failed/failing bolt > will be replayed, and the failed bolt executor will be restarted within a > new worker process. > > --John > > On Tue, Jan 19, 2016 at 12:18 PM, Noppanit Charassinvichai < > [email protected]> wrote: > >> Thanks for your reply. So that means if I don't do any fieldsGrouping. >> The bolt that fails will be replayed? >> >> Because my topology only uses shuffleGrouping. >> >> Thanks very much. >> >> >> >> On Tue, 19 Jan 2016 at 11:00 John Yost <[email protected]> wrote: >> >>> Storm would replay the tuple and there is no guarantee which bolt it >>> goes to unless you are using fieldsGrouping. >>> >>> --John >>> >>> On Tue, Jan 19, 2016 at 10:56 AM, Noppanit Charassinvichai < >>> [email protected]> wrote: >>> >>>> Also, if I have one spout and two bolts. If both two bolts call ack() >>>> and if one of them fail. Would the tuple will be replayed only for just >>>> that bolt? Or both of the bolts? >>>> >>>> On Tue, 19 Jan 2016 at 10:42 John Yost <[email protected]> wrote: >>>> >>>>> Yes, acking a tuple confirms to Storm that a tuple was processed >>>>> within a Spout or Bolt, and is used to guarantee at least once processing >>>>> for all tuples processed by your topology. >>>>> >>>>> --John >>>>> >>>>> On Tue, Jan 19, 2016 at 9:49 AM, Noppanit Charassinvichai < >>>>> [email protected]> wrote: >>>>> >>>>>> I'm new to Storm. And I've seen some of the examples that do not call >>>>>> `ack()` in Bolt. From the documentation and my understanding, is calling >>>>>> ack() is just for guaranteeing that the msg will be processed at least >>>>>> once? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>> >>> >
