Tang :
>
>> Hi Alex,
>>
>> I think the better solution is to know what the problem you have ever met
>> when restoring the timers?
>>
>> Flink does not support to remove state (including timer state) currently.
>>
>> Best
>> Yun Tang
>>
*Sent:* Monday, February 7, 2022 21:09
*To:* Caizhi Weng
*Cc:* User-Flink
*Subject:* Re: How to prevent check pointing of timers ?
By timer I mean regular timer from KeyedState which utilized via
function onTimer, for example:
public class StateWithTimer {
p
ave ever met
> when restoring the timers?
>
> Flink does not support to remove state (including timer state) currently.
>
> Best
> Yun Tang
> --
> *From:* Alex Drobinsky
> *Sent:* Monday, February 7, 2022 21:09
> *To:* Caizhi Weng
> *Cc
To: Caizhi Weng
Cc: User-Flink
Subject: Re: How to prevent check pointing of timers ?
By timer I mean regular timer from KeyedState which utilized via function
onTimer, for example:
public class StateWithTimer {
public long timerValue = 0;
public volatile boolean shouldResetTimer = true
By timer I mean regular timer from KeyedState which utilized via function
onTimer, for example:
public class StateWithTimer {
public long timerValue = 0;
public volatile boolean shouldResetTimer = true;
public boolean resetIfMust(long timeoutInMilliseconds,
TimerService
Hi!
Could you elaborate more on your code or share it if possible? Which timer
are you talking about? Are you using the data stream API or SQL API? Do you
mean the timer registered per record for a window aggregation? Does mini
batch aggregation [1] solve your problem?
[1]
Dear flink user,
In our project, restoring the timer's state creates numerous issues, so I
would like to know
if it is possible to avoid save/restore of timers altogether.
If it isn't possible, how could I delete all registered timers during the
open function ?
Best regards,
Alexander
