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] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node
Date Wed, 18 Feb 2015 09:09:12 GMT

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

Rohith updated YARN-3194:
-------------------------
    Summary: After NM restart, RM should handle NMCotainerStatuses sent by NM while registering
if NM is Reconnected node  (was: After NM restart,completed containers are not released by
RM which are sent during NM registration)

> After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if
NM is Reconnected node
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3194
>                 URL: https://issues.apache.org/jira/browse/YARN-3194
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.0
>         Environment: NM restart is enabled
>            Reporter: Rohith
>            Assignee: Rohith
>            Priority: Blocker
>         Attachments: 0001-yarn-3194-v1.patch
>
>
> 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