[
https://issues.apache.org/jira/browse/FLINK-19069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189933#comment-17189933
]
Robert Metzger commented on FLINK-19069:
----------------------------------------
Ah, thanks for the explanation!
Can we execute the {{finalizeOnMaster()}} call on the {{ioExecutor}} pool of
the {{ExecutionGraph}}, and do the RUNNING -> FINISHED state transition (in the
main thread) once the method has completed? (I'm not sure what's allowed in
terms of concurrency in the ExecutionGraph)
(There is actually a comment in the code that implies that my proposal is
implemented, but I don't think that comment is true)
> finalizeOnMaster takes too much time and client timeouts
> --------------------------------------------------------
>
> Key: FLINK-19069
> URL: https://issues.apache.org/jira/browse/FLINK-19069
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.9.0, 1.10.0, 1.11.0, 1.12.0
> Reporter: Jiayi Liao
> Priority: Critical
> Fix For: 1.12.0, 1.11.2, 1.10.3
>
>
> Currently we execute {{finalizeOnMaster}} in JM's main thread, which may
> stuck the JM for a very long time and client timeouts eventually.
> For example, we'd like to write data to HDFS and commit files on JM, which
> takes more than ten minutes to commit tens of thousands files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
