[ https://issues.apache.org/jira/browse/FLINK-13698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330080#comment-17330080 ]
Till Rohrmann commented on FLINK-13698: --------------------------------------- What is the state of this problem [~pnowojski]. I think we should raise the priority of this ticket to critical because it causes cluster instabilities which are quite serious. I think we should try to solve this problem eventually. > Rework threading model of CheckpointCoordinator > ----------------------------------------------- > > Key: FLINK-13698 > URL: https://issues.apache.org/jira/browse/FLINK-13698 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing > Affects Versions: 1.10.0 > Reporter: Piotr Nowojski > Priority: Major > Fix For: 1.13.0 > > > Currently {{CheckpointCoordinator}} and {{CheckpointFailureManager}} code is > executed by multiple different threads (mostly {{ioExecutor}}, but not only). > It's causing multiple concurrency issues, for example: > https://issues.apache.org/jira/browse/FLINK-13497 > Proper fix would be to rethink threading model there. At first glance it > doesn't seem that this code should be multi threaded, except of parts doing > the actual IO operations, so it should be possible to run everything in one > single ExecutionGraph's thread and just run asynchronously necessary IO > operations with some feedback loop ("mailbox style"). > I would strongly recommend fixing this issue before adding new features in > the \{{CheckpointCoordinator}} component. -- This message was sent by Atlassian Jira (v8.3.4#803005)