Thank you for your answer, Ambud. My use case is that only some of the bolt instances are critical that I need them responding to the signal through proper acknowledgment. However, the rest of them are non-critical which are preferably not to interfere the normal ack process, much like receiving an unanchored tuple. Is there any way that I can achieve this?
On 20 December 2016 at 11:01, Ambud Sharma <[email protected]> wrote: > Forgot to answer your specific question. Storm message id is internal and > will be different so you will see a duplicate tuple with a different id. > > On Dec 19, 2016 3:59 PM, "Ambud Sharma" <[email protected]> wrote: > >> Yes that is correct. All downstream tuples must be processed for the root >> tuple to be acknowledged. >> >> Type of grouping does not change the acking behavior. >> >> On Dec 19, 2016 3:53 PM, "Xunyun Liu" <[email protected]> wrote: >> >>> Hi there, >>> >>> As some grouping methods allow sending multiple copies of emitted data >>> to downstream bolt instances, I was wondering what will happen if any one >>> of them is not able to ack the tuple due to failures. The intrinsic >>> question is that, when the all grouping method is used, whether the >>> recipients are receiving the exact the same tuple or just duplications with >>> different tuple IDs. In the latter case, I believe the tuple tree is >>> expanded with regard to the number of parallelisms in downstream and each >>> task has to invoke ack() for the root tuple to be fully processed. >>> >>> Any idea is much appreciated. >>> >>> >>> -- >>> Best Regards. >>> ====================================================== >>> Xunyun Liu >>> >>> >>> -- Best Regards. ====================================================== Xunyun Liu The Cloud Computing and Distributed Systems (CLOUDS) Laboratory, The University of Melbourne
