[ https://issues.apache.org/jira/browse/YARN-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594300#comment-14594300 ]
Jun Gong commented on YARN-3809: -------------------------------- [~jlowe] Thank you for the very detailed suggestions. It helps me a lot. I will update patch to address your suggestions. I find it might be better to change config in ApplicationMasterLauncher#serviceInit, then we just need change it one time, all newly created AMLauncher will use this config. > Failed to launch new attempts because ApplicationMasterLauncher's threads all > hang > ---------------------------------------------------------------------------------- > > Key: YARN-3809 > URL: https://issues.apache.org/jira/browse/YARN-3809 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager > Reporter: Jun Gong > Assignee: Jun Gong > Attachments: YARN-3809.01.patch, YARN-3809.02.patch > > > ApplicationMasterLauncher create a thread pool whose size is 10 to deal with > AMLauncherEventType(LAUNCH and CLEANUP). > In our cluster, there was many NM with 10+ AM running on it, and one shut > down for some reason. After RM found the NM LOST, it cleaned up AMs running > on it. Then ApplicationMasterLauncher need handle these 10+ CLEANUP event. > ApplicationMasterLauncher's thread pool would be filled up, and they all hang > in the code containerMgrProxy.stopContainers(stopRequest) because NM was > down, the default RPC time out is 15 mins. It means that in 15 mins > ApplicationMasterLauncher could not handle new event such as LAUNCH, then new > attempts will fails to launch because of time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)