You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2019/03/29 01:47:00 UTC

[jira] [Assigned] (FLINK-12058) Cancel checkpoint operations belonging to a discarded/aborted checkpoint

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

vinoyang reassigned FLINK-12058:
--------------------------------

    Assignee: vinoyang

> Cancel checkpoint operations belonging to a discarded/aborted checkpoint
> ------------------------------------------------------------------------
>
>                 Key: FLINK-12058
>                 URL: https://issues.apache.org/jira/browse/FLINK-12058
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Checkpointing
>    Affects Versions: 1.7.2, 1.8.0
>            Reporter: Till Rohrmann
>            Assignee: vinoyang
>            Priority: Major
>
> In order to save CPU cycles and reduce disk and network I/O, we should try to cancel local checkpoint operations belonging to discarded aborted or subsumed checkpoints. For example, if a {{Task}} declines a checkpoint, the {{CheckpointCoordinator}} will discard this checkpoint. However, other checkpointing operations belonging to this checkpoint won't be necessarily notified and canceled.
> The notification mechanism could piggy back on the existing {{CancelCheckpointMarker}} or be a separate signal sent to all participating {{Tasks}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)