hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3987) am container complete msg ack to NM once RM receive it
Date Fri, 14 Aug 2015 14:36:54 GMT

    [ https://issues.apache.org/jira/browse/YARN-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697120#comment-14697120

Hudson commented on YARN-3987:

FAILURE: Integrated in Hadoop-Hdfs-trunk #2214 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2214/])
YARN-3987. Send AM container completed msg to NM once AM finishes. Contributed by sandflee
(jianhe: rev 0a030546e24c55662a603bb63c9029ad0ccf43fc)
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/RMAppAttemptImpl.java

> 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
>            Assignee: sandflee
>             Fix For: 2.8.0
>         Attachments: YARN-3987.001.patch, YARN-3987.002.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

View raw message