[
https://issues.apache.org/jira/browse/FLINK-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328820#comment-17328820
]
Flink Jira Bot commented on FLINK-5960:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Make CheckpointCoordinator less blocking
> ----------------------------------------
>
> Key: FLINK-5960
> URL: https://issues.apache.org/jira/browse/FLINK-5960
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.2.0, 1.3.0, 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Major
> Labels: stale-major
>
> Currently the {{CheckpointCoordinator}} locks its operation under a global
> lock. This also includes writing checkpoint data out to a state storage. If
> this operation blocks, then the whole checkpoint operator stands still. I
> think we should rework the {{CheckpointCoordinator}} to make fewer
> assumptions about external systems to tolerate write failures and timeouts.
> Furthermore, we should try to limit the scope of locking and the execution of
> potentially blocking operation under the lock. This will improve the runtime
> behaviour of the {{CheckpointCoordinator}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
