Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 31 Dec 2014 02:10:13 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12764140.1419921140000.119197.1419991813458@Atlassian.JIRA>
In-Reply-To: <JIRA.12764140.1419921140000@Atlassian.JIRA>
References: <JIRA.12764140.1419921140000@Atlassian.JIRA>
 <JIRA.12764140.1419921140144@arcas>
Subject: [jira] [Commented] (YARN-2997) NM keeps sending finished containers
 to RM until app is finished
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jian He commented on YARN-2997:
-------------------------------

bq. The uploaded patch will let the normal heartbeat
The intention was to let NM remove containers from its context only after RM acks it has received these containers. More context in YARN-1372

> NM keeps sending finished containers to RM until app is finished
> ----------------------------------------------------------------
>
>                 Key: YARN-2997
>                 URL: https://issues.apache.org/jira/browse/YARN-2997
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.6.0
>            Reporter: Chengbing Liu
>         Attachments: YARN-2997.patch
>
>
> We have seen in RM log a lot of
> {quote}
> INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: Null container completed...
> {quote}
> It is caused by NM sending completed containers repeatedly until the app is finished. On the RM side, the container is already released, hence {{getRMContainer}} returns null.


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