Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 7 Nov 2014 00:59:33 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12753577.1415321915000.440762.1415321973688@Atlassian.JIRA>
In-Reply-To: <JIRA.12753577.1415321915000@Atlassian.JIRA>
References: <JIRA.12753577.1415321915000@Atlassian.JIRA>
 <JIRA.12753577.1415321915090@arcas>
Subject: [jira] [Created] (YARN-2825) Container leak on NM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jian He created YARN-2825:
-----------------------------

             Summary: Container leak on NM
                 Key: YARN-2825
                 URL: https://issues.apache.org/jira/browse/YARN-2825
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Jian He
            Assignee: Jian He
            Priority: Critical


Caused by YARN-1372. thanks [~vinodkv] for pointing  this out.

The problem is that in YARN-1372 we changed the behavior to remove containers from NMContext only after the containers are acknowledged  by AM. But in the {{NodeStatusUpdaterImpl#removeCompletedContainersFromContext}} call, we didn't check whether the container is really completed or not.  If the container is stilll running, we shouldn't remove the container from the context


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