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 "Junping Du (JIRA)" <ji...@apache.org> on 2016/12/01 23:16:58 UTC
[jira] [Commented] (YARN-5197) RM leaks containers if running
container disappears from node update
[ https://issues.apache.org/jira/browse/YARN-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713384#comment-15713384 ]
Junping Du commented on YARN-5197:
----------------------------------
I think the patch goes to branch-2.8 as well. Add 2.8 in fix version.
> 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.7.2, 2.6.4
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Fix For: 2.6.5, 2.7.4
>
> Attachments: YARN-5197-branch-2.7.003.patch, YARN-5197-branch-2.8.003.patch, YARN-5197.001.patch, YARN-5197.002.patch, YARN-5197.003.patch
>
>
> 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org