[
https://issues.apache.org/jira/browse/YARN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091583#comment-14091583
]
Hadoop QA commented on YARN-2249:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12660744/YARN-2249.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-tools/hadoop-sls
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4567//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4567//console
This message is automatically generated.
> RM may receive container release request on AM resync before container is
> actually recovered
> --------------------------------------------------------------------------------------------
>
> 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
>
>
> 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)
