Re: allowNonRestoredState doesn't seem to be working

k8s-checkpoint-test-k8s-deploy/000000000000/chk-34. >> >> -- >> *От:* Gyula Fóra >> *Отправлено:* 13 октября 2022 г. 13:19:54 >> *Кому:* Yaroslav Tkachenko >> *Копия:* user >> *Тема:* Re: allowNonRestoredState doesn

Re: allowNonRestoredState doesn't seem to be working

> *От:* Gyula Fóra > *Отправлено:* 13 октября 2022 г. 13:19:54 > *Кому:* Yaroslav Tkachenko > *Копия:* user > *Тема:* Re: allowNonRestoredState doesn't seem to be working > > Hi! > > If you have last-state upgrade mode configured it may happen that the > allowNonRe

Re: allowNonRestoredState doesn't seem to be working

doesn't seem to be working Hi! If you have last-state upgrade mode configured it may happen that the allowNonRestoredState config is ignored by Flink (as the last-state upgrade mechanism somewhat bypasses the regular submission). Worst case scenario, you can suspend the deployment, manually r

Re: allowNonRestoredState doesn't seem to be working

Hi! If you have last-state upgrade mode configured it may happen that the allowNonRestoredState config is ignored by Flink (as the last-state upgrade mechanism somewhat bypasses the regular submission). Worst case scenario, you can suspend the deployment, manually record the last checkpoint/savep

allowNonRestoredState doesn't seem to be working

Hey everyone, I'm trying to redeploy an application using a savepoint. The new version of the application has a few operators with new uids and a few operators with the old uids. I'd like to keep the state for the old ones. I passed the allowNonRestoredState flag (using Apache Kubernetes Operator