State Recovery Configuration

Key	Default	Type	Description

execution.state-recovery.claim-mode

| NO_CLAIM |

Enum

| Describes the mode how Flink should restore from the given savepoint or retained checkpoint.

Possible values:

• "CLAIM": Flink will take ownership of the given snapshot. It will clean the snapshot once it is subsumed by newer ones.
• "NO_CLAIM": Flink will not claim ownership of the snapshot files. However it will make sure it does not depend on any artefacts from the restored snapshot. In order to do that, Flink will take the first checkpoint as a full one, which means it might reupload/duplicate files that are part of the restored checkpoint.

| |

execution.state-recovery.from-local

| false | Boolean | This option configures local recovery for the state backend, which indicates whether to recovery from local snapshot.By default, local recovery is deactivated. Local recovery currently only covers keyed state backends (including both the EmbeddedRocksDBStateBackend and the HashMapStateBackend)." | |

execution.state-recovery.ignore-unclaimed-state

| false | Boolean | Allow to skip savepoint state that cannot be restored. Allow this if you removed an operator from your pipeline after the savepoint was triggered. | |

execution.state-recovery.path

| (none) | String | Path to a savepoint to restore the job from (for example hdfs:///flink/savepoint-1537). | |

execution.state-recovery.without-channel-state.checkpoint-id

| -1 | Long | Checkpoint id for which in-flight data should be ignored in case of the recovery from this checkpoint.

It is better to keep this value empty until there is explicit needs to restore from the specific checkpoint without in-flight data.
|