The checkpoint tuples have to go through the same queue and follow the tuples emitted before it to make the state consistent across the bolts.
When bolt ‘A’ receives a checkpoint (say C1 from the spout), it saves its state (of processing the tuples up to C1) and emits ’C1’ to the next bolt say Bolt B. Now bolt B should process all the previous tuples emitted by A first before it processes ‘C1’ so that the sate saved at A and B represents the state that’s the result of all the the tuples that arrived from the spout before C1. Thanks, Arun From: anshu shukla <anshushuk...@gmail.com> Reply-To: "user@storm.apache.org" <user@storm.apache.org> Date: Saturday, March 25, 2017 at 1:39 PM To: "user@storm.apache.org" <user@storm.apache.org> Subject: Delay in CHKPT message for stateful task Hello , I was worrying that since CHKPT messages go thru the same queues as the actual tuples and in the case of large topology with many in/out queues(disruptor) it will take a long time for CHKPT tuple to reach the last stateful bolt in the topology. So Is there any way to give priority to the CHKPT msg so that it passes on fastly. So that even in case of congestion we can have safe CHKPTing. -- Thanks & Regards, Anshu Shukla
