hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2249) AM release request may be lost on RM restart
Date Tue, 19 Aug 2014 20:23:20 GMT

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

Zhijie Shen commented on YARN-2249:
-----------------------------------

+1 for the latest patch. Will commit it.

> AM release request may be lost on RM restart
> --------------------------------------------
>
>                 Key: YARN-2249
>                 URL: https://issues.apache.org/jira/browse/YARN-2249
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Jian He
>            Assignee: Jian He
>         Attachments: YARN-2249.1.patch, YARN-2249.1.patch, YARN-2249.2.patch, YARN-2249.2.patch,
YARN-2249.3.patch, YARN-2249.4.patch, YARN-2249.5.patch
>
>
> AM resync on RM restart will send outstanding container release requests back to the
new RM. In the meantime, NMs report the container statuses back to RM to recover the containers.
If RM receives the container release request  before the container is actually recovered in
scheduler, the container won't be released and the release request will be lost.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message