You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2020/01/21 08:18:00 UTC
[jira] [Closed] (FLINK-13905) Separate checkpoint triggering into
stages
[ https://issues.apache.org/jira/browse/FLINK-13905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Nowojski closed FLINK-13905.
----------------------------------
Resolution: Fixed
Merged into master as e1c9ede67c7963e458b7d84243581996aa0d27f8..0352fa595c57c3ccfaf31bc8f44be8107c4485bf
> Separate checkpoint triggering into stages
> ------------------------------------------
>
> Key: FLINK-13905
> URL: https://issues.apache.org/jira/browse/FLINK-13905
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Checkpointing
> Reporter: Biao Liu
> Assignee: Biao Liu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently {{CheckpointCoordinator#triggerCheckpoint}} includes some heavy IO operations. We plan to separate the triggering into different stages. The IO operations are executed in IO threads, while other on-memory operations are not.
> This is a preparation for making all on-memory operations of {{CheckpointCoordinator}} single threaded (in main thread).
> Note that we could not put on-memory operations of triggering into main thread directly now. Because there are still some operations on a heavy lock (coordinator-wide).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)