[
https://issues.apache.org/jira/browse/YARN-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899446#comment-13899446
]
Hadoop QA commented on YARN-1417:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628531/YARN-1417.3.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 2 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 1.3.9) 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-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/3084//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3084//console
This message is automatically generated.
> RM may issue expired container tokens to AM while issuing new containers.
> -------------------------------------------------------------------------
>
> Key: YARN-1417
> URL: https://issues.apache.org/jira/browse/YARN-1417
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Omkar Vinit Joshi
> Assignee: Jian He
> Priority: Blocker
> Attachments: YARN-1417.2.patch, YARN-1417.3.patch
>
>
> Today we create new container token when we create container in RM as a part
> of schedule cycle. However that container may get reserved or assigned. If
> the container gets reserved and remains like that (in reserved state) for
> more than container token expiry interval then RM will end up issuing
> container with expired token.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
