[
https://issues.apache.org/jira/browse/FLINK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409961#comment-15409961
]
Stephan Ewen commented on FLINK-4322:
-------------------------------------
I would like to make some more radical changes to the current checkpoint /
savepoint design.
- There should be no difference at all between checkpoint and savepoint any
more.
- A savepoint is merely a parameterized checkpoint (with a future to announce
its result)
- There is no SavepointCoordinator any more
- a savepoint restore simply adds a completed checkpoint to the checkpoint
coordinator
The execution graph code should become very simple that way.
Since that is a pretty deep change in the checkpointing mechanism, I would be
happy to actually take this over.
> Unify CheckpointCoordinator and SavepointCoordinator
> ----------------------------------------------------
>
> Key: FLINK-4322
> URL: https://issues.apache.org/jira/browse/FLINK-4322
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Affects Versions: 1.1.0
> Reporter: Stephan Ewen
> Fix For: 1.2.0
>
>
> The Checkpoint coordinator should have the functionality of both handling
> checkpoints and savepoints.
> The difference between checkpoints and savepoints is minimal:
> - savepoints always write the root metadata of the checkpoint
> - savepoints are always full (never incremental)
> The commonalities are large
> - jobs should be able to resume from checkpoint or savepoints
> - jobs should fall back to the latest checkpoint or savepoint
> This subsumes issue https://issues.apache.org/jira/browse/FLINK-3397
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
