[ https://issues.apache.org/jira/browse/FLINK-4620 ]
Hangxiang Yu deleted comment on FLINK-4620: ------------------------------------- was (Author: masteryhx): Close this as no intention in this direction just like FLINK-4511. Considering current design of checkpoint and savepoint, I also think it's better to implement this in the platform or like K8s operator which has supported this [1]. Please reopen it if necessary. [1] [https://nightlies.apache.org/flink/flink-docs-release-1.17/docs/ops/state/checkpoints_vs_savepoints/] [2] [https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.6/docs/custom-resource/job-management/#periodic-savepoint-triggering] > Automatically creating savepoints > --------------------------------- > > Key: FLINK-4620 > URL: https://issues.apache.org/jira/browse/FLINK-4620 > Project: Flink > Issue Type: New Feature > Components: Runtime / State Backends > Affects Versions: 1.1.2 > Reporter: Niels Basjes > Priority: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor > > In the current versions of Flink you can run an external command and then a > savepoint is persisted in a durable location. > Feature request: Make this a lot more automatic and easy to use. > _Proposed workflow_ > # In my application I do something like this: > {code} > StreamExecutionEnvironment env = > StreamExecutionEnvironment.getExecutionEnvironment(); > env.setStateBackend(new FsStateBackend("hdfs:///tmp/applicationState")); > env.enableCheckpointing(5000, CheckpointingMode.EXACTLY_ONCE); > env.enableAutomaticSavePoints(300000); > env.enableAutomaticSavePointCleaner(10); > {code} > # When I start the application for the first time the state backend is > 'empty'. > I expect the system to start in a clean state. > After 10 minutes (300000ms) a savepoint is created and stored. > # When I stop and start the topology again it will automatically restore the > last available savepoint. > Things to think about: > * Note that this feature still means the manual version is useful!! > * What to do on startup if the state is incompatible with the topology? Fail > the startup? > * How many automatic savepoints to we keep? Only the last one? > * Perhaps the API should allow multiple automatic savepoints at different > intervals in different locations. > {code} > // Make every 10 minutes and keep the last 10 > env.enableAutomaticSavePoints(300000, new > FsStateBackend("hdfs:///tmp/applicationState"), 10); > // Make every 24 hours and keep the last 30 > // Useful for being able to reproduce a problem a few days later > env.enableAutomaticSavePoints(86400000, new > FsStateBackend("hdfs:///tmp/applicationDailyStateSnapshot"), 30); > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)