Details
-
New Feature
-
Status: Closed
-
Not a Priority
-
Resolution: Not A Problem
-
1.1.2
-
None
Description
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:
StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment(); env.setStateBackend(new FsStateBackend("hdfs:///tmp/applicationState")); env.enableCheckpointing(5000, CheckpointingMode.EXACTLY_ONCE); env.enableAutomaticSavePoints(300000); env.enableAutomaticSavePointCleaner(10);
- 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.
// 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);
Attachments
Issue Links
- is related to
-
FLINK-4511 Schedule periodic savepoints
- Closed