flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4322) Unify CheckpointCoordinator and SavepointCoordinator
Date Thu, 18 Aug 2016 09:42:21 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426167#comment-15426167

ASF GitHub Bot commented on FLINK-4322:

Github user ramkrish86 commented on the issue:

    Reading the code once again, just few doubts/questions
    ->If a save point is triggered and that is happening with in the duration of the 'MINIMUM_TIME_BETWEEN_CHECKPOINTS'
we still throw back a decline result? Is it not needed that since Save points are externally
triggered we need to isolate that with the internal timing we maintain? 
    Correct me if am missing something here. Thanks. 

> Unify CheckpointCoordinator and SavepointCoordinator
> ----------------------------------------------------
>                 Key: FLINK-4322
>                 URL: https://issues.apache.org/jira/browse/FLINK-4322
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.1.0
>            Reporter: Stephan Ewen
>            Assignee: 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

View raw message