hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3194) After NM restart,completed containers are not released which are sent during NM registration
Date Sun, 15 Feb 2015 18:58:12 GMT

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

Rohith commented on YARN-3194:
------------------------------

And Not related specific to this jira, I have one doubt on this method {{ResourceTrackerService#handleNMContainerStatus}}
is sending container_finished event only to master container. Why other containers are not
considered? I think it is made intentionally for optimization so if container_finished event
would release other containers resources. Is this is the reason?

> After NM restart,completed containers are not released which are sent during NM registration
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-3194
>                 URL: https://issues.apache.org/jira/browse/YARN-3194
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>         Environment: NM restart is enabled
>            Reporter: Rohith
>            Assignee: Rohith
>
> On NM restart ,NM sends all the outstanding NMContainerStatus to RM. But RM process only
ContainerState.RUNNING. If container is completed when NM was down then those containers resources
wont be release which result in applications to hang.



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

Mime
View raw message