You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/01/04 16:12:00 UTC

[jira] [Updated] (FLINK-20846) Decouple checkpoint services from CheckpointCoordinator

     [ https://issues.apache.org/jira/browse/FLINK-20846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-20846:
-----------------------------------
    Labels: pull-request-available  (was: )

> Decouple checkpoint services from CheckpointCoordinator
> -------------------------------------------------------
>
>                 Key: FLINK-20846
>                 URL: https://issues.apache.org/jira/browse/FLINK-20846
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.13.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0
>
>
> In order to reuse checkpoints across different {{ExecutionGraph}} instances (w/o HA), we need to decouple the checkpoint services {{CompletedCheckpointStore}} and {{CheckpointIDCounter}} from the {{CheckpointCoordinator}}. The reason is that the {{CheckpointCoordinator}} is bound to the lifetime of an {{ExecutionGraph}} and shuts the services down once the {{ExecutionGraph}} reaches a terminal state. Once this is no longer the case, it would be possible to create a new {{ExecutionGraph}} which can resume from a previous checkpoint if the appropriate {{CompletedCheckpointStore}} is provided.
> For future scheduler implementations which want to reuse the {{ExecutionGraph}} but need to create different instances this is a requirement to support state recovery.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)