Hi Team, I am using context.timerService() in keyedProcessFunction to schedule the timer for a future time and then onTimer() will be called at a scheduled time. Here I'm using Kubernetes PVC for RocksDB as the state backend. Now when we schedule the timer for a future time and in-between if our pod get down and restarted again, the pod will not be able to trigger the onTimer() function at the scheduled time, even though we use PV for RocksDB as state backend. As per documentation, the timer will get restored when the pod gets restarted. Can anyone help me with this? Thanks.

timer state is stored in rocksdb so it should be restored.. are u using the flink kube operator?

Yes

i would suggest posting this to the flink user mailing list.. it might be something relevant to the operator, so they might have more context on this.

hey @Giannis Polyzos here https://github.com/kubernetes/kubernetes/issues/118900 I mentioned what we exactly doing and what is expected.

unfortunately i haven't tested this on the operator to able to help more

okay @Giannis Polyzos, you can check above mentioned open issue ticket for more context.

@Abhishek Joshi I seen that you are @ multiple people in this thread. That's against the rules, as stated in this channel specifically. It will result in removal of the post/your account next time.