You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yumeng Zhang (Jira)" <ji...@apache.org> on 2020/08/07 10:04:00 UTC
[jira] [Commented] (FLINK-16069) Creation of
TaskDeploymentDescriptor can block main thread for long time
[ https://issues.apache.org/jira/browse/FLINK-16069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173036#comment-17173036 ]
Yumeng Zhang commented on FLINK-16069:
--------------------------------------
Hello guys, do you reach a consensus about how to optimize creating TaskDeploymentDescriptor?
> Creation of TaskDeploymentDescriptor can block main thread for long time
> ------------------------------------------------------------------------
>
> Key: FLINK-16069
> URL: https://issues.apache.org/jira/browse/FLINK-16069
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: huweihua
> Priority: Major
>
> The deploy of tasks will take long time when we submit a high parallelism job. And Execution#deploy run in mainThread, so it will block JobMaster process other akka messages, such as Heartbeat. The creation of TaskDeploymentDescriptor take most of time. We can put the creation in future.
> For example, A job [source(8000)->sink(8000)], the total 16000 tasks from SCHEDULED to DEPLOYING took more than 1mins. This caused the heartbeat of TaskManager timeout and job never success.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)