Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 2 Jun 2016 21:47:59 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12975314.1464904077000.19952.1464904079162@Atlassian.JIRA>
In-Reply-To: <JIRA.12975314.1464904077000@Atlassian.JIRA>
References: <JIRA.12975314.1464904077000@Atlassian.JIRA> <JIRA.12975314.1464904077430@arcas>
Subject: [jira] [Created] (YARN-5197) RM leaks containers if running
 container disappears from node update
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Jun 2016 21:48:01 -0000

Jason Lowe created YARN-5197:
--------------------------------

             Summary: RM leaks containers if running container disappears from node update
                 Key: YARN-5197
                 URL: https://issues.apache.org/jira/browse/YARN-5197
             Project: Hadoop YARN
          Issue Type: Bug
          Components: resourcemanager
    Affects Versions: 2.6.4, 2.7.2
            Reporter: Jason Lowe
            Assignee: Jason Lowe


Once a node reports a container running in a status update, the corresponding RMNodeImpl will track the container in its launchedContainers map.  If the node somehow misses sending the completed container status to the RM and the container simply disappears from subsequent heartbeats, the container will leak in launchedContainers forever and the container completion event will not be sent to the scheduler.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org