Hello,

When deleting an operator we run our application with 
--allowNonRestoredState=true, as described in the 
documentation<https://ci.apache.org/projects/flink/flink-docs-stable/ops/state/savepoints.html#what-happens-if-i-delete-an-operator-that-has-state-from-my-job>.
 When running with this flag, we have observed that the _metadata file is not 
generated in the checkpoint directory. So, if the application fails, we don’t 
have the ability to start from the checkpoint. And since the application has 
failed, we can’t take a savepoint as well.


Is _metadata file not being created in this case expected behavior?

How do we achieve resilience while using --allowNonRestoredState?


We are using Beam with the Flink runner(java).

  *   Beam 2.19

  *   Flink 1.9

Omkar

Reply via email to