rm.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 t
rch 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
>
huk...@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
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
