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

Daniel Ma updated YARN-11401:
-----------------------------
    Description: 
Currently, there is only one thread pool to handle AM launch and cleanup event 
by ResourceManager, 
In some cases, too many cleanup event will lead to AM launch stuck for a long 
time.
So in this patch, We divide the shared thread pool into two separated ones to 
handle different event in case that cleanup event flood in blocking launcher 
events being timely handled and vise versa.

  was:
Currently, there is only one thread pool to handle AM launch and cleanup event 
by ResourceManager, 
In some cases, too many cleanup event will lead to AM launch stuck for a long 
time.
So in this patch, We divide the shared thread pool into two separated ones to 
handle different event in case that a flood event of one kind may block other 
kinds for a long time.


> Separate AppMaster cleanup events and launcher event into different resource 
> pools
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-11401
>                 URL: https://issues.apache.org/jira/browse/YARN-11401
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Daniel Ma
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, there is only one thread pool to handle AM launch and cleanup 
> event by ResourceManager, 
> In some cases, too many cleanup event will lead to AM launch stuck for a long 
> time.
> So in this patch, We divide the shared thread pool into two separated ones to 
> handle different event in case that cleanup event flood in blocking launcher 
> events being timely handled and vise versa.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to