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

Posted to yarn-issues@hadoop.apache.org by "sandflee (JIRA)" <ji...@apache.org> on 2015/07/28 17:32:05 UTC

[jira] [Updated] (YARN-3987) am container complete msg ack to NM once RM receive it

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

sandflee updated YARN-3987:
---------------------------
    Attachment: YARN-3987.001.patch

> am container complete msg ack to NM once RM receive it
> ------------------------------------------------------
>
>                 Key: YARN-3987
>                 URL: https://issues.apache.org/jira/browse/YARN-3987
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: sandflee
>         Attachments: YARN-3987.001.patch
>
>
> In our cluster we set max-am-attempts to a very very large num, and unfortunately our am crash after launched, leaving too many completed container(AM container) in NM.  completed container is removed from NM and NMStateStore only if container complete is passed to AM, but if AM couldn't be launched, the completed AM container couldn't be cleaned, and may eat up  NM heap memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)