You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/11/07 09:28:03 UTC

[jira] [Updated] (FLINK-13184) Starting a TaskExecutor blocks the YarnResourceManager's main thread

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

Till Rohrmann updated FLINK-13184:
----------------------------------
    Summary: Starting a TaskExecutor blocks the YarnResourceManager's main thread  (was: Support launching task executors with multi-thread on YARN.)

> Starting a TaskExecutor blocks the YarnResourceManager's main thread
> --------------------------------------------------------------------
>
>                 Key: FLINK-13184
>                 URL: https://issues.apache.org/jira/browse/FLINK-13184
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>    Affects Versions: 1.8.1, 1.9.0
>            Reporter: Xintong Song
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, YarnResourceManager starts all task executors in main thread. This could cause RM thread becomes unresponsive when launching a large number of TEs (e.g. > 1000), leading to TE registration/heartbeat timeouts.
>  
> In Blink, we have a thread pool that RM starts TEs through the YARN NMClient in separated threads. I think we should add this feature to the Flink master branch as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)