[jira] [Updated] (FLINK-13904) Avoid competition between different rounds of checkpoint triggering

["Till Rohrmann (Jira)" <ji...@apache.org>]

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

Till Rohrmann updated FLINK-13904:
----------------------------------
    Component/s:     (was: Runtime / Coordination)
                 Runtime / Checkpointing

> Avoid competition between different rounds of checkpoint triggering
> -------------------------------------------------------------------
>
>                 Key: FLINK-13904
>                 URL: https://issues.apache.org/jira/browse/FLINK-13904
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Checkpointing
>            Reporter: Biao Liu
>            Priority: Major
>             Fix For: 1.10.0
>
>
> As a part of {{CheckpointCoordinator}} refactoring, I'd like to simplify the concurrent triggering logic.
> The different rounds of checkpoint triggering would be processed sequentially. The final target is getting rid of timer thread and {{triggerLock}}.
> Note that we can't avoid all competitions of triggering for now. There is still a competition between normal checkpoint triggering and savepoint triggering. We could avoid this competition by executing triggering in main thread. But it could not be achieved until all blocking operations are handled well in IO threads.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)