You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2016/08/05 17:55:20 UTC
[jira] [Commented] (FLINK-4322) Unify CheckpointCoordinator and
SavepointCoordinator
[ https://issues.apache.org/jira/browse/FLINK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409799#comment-15409799 ]
ramkrishna.s.vasudevan commented on FLINK-4322:
-----------------------------------------------
bq.jobs should be able to resume from checkpoint or savepoints
bq.jobs should fall back to the latest checkpoint or savepoint
Ya this is what FLINK-3397 tries to achieve too.
[~uce] had given some comments and I had update the document but not yet uploaded in that JIRa. He was also telling about job and save point mapping. I had raised some comments and doubts regarding that in the other JIRA. As he is very busy just waiting for his inputs. As this and FLINK-3397 are related am happy to work on these and will do after we are arriving at a consensus on the design part. Thanks.
> 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)