hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5197) RM leaks containers if running container disappears from node update
Date Fri, 28 Jul 2017 21:17:00 GMT

     [ https://issues.apache.org/jira/browse/YARN-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-5197:
------------------------------------------
    Priority: Critical  (was: Major)

> 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
>            Priority: Critical
>             Fix For: 2.8.0, 2.6.5, 2.7.4
>
>         Attachments: YARN-5197.001.patch, YARN-5197.002.patch, YARN-5197.003.patch, YARN-5197-branch-2.7.003.patch,
YARN-5197-branch-2.8.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.4.14#64029)

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


Mime
View raw message