[
https://issues.apache.org/jira/browse/YARN-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481876#comment-13481876
]
Hadoop QA commented on YARN-180:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550355/YARN-180.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
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/113//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/113//console
This message is automatically generated.
> Capacity scheduler - containers that get reserved create container token to
> early
> ---------------------------------------------------------------------------------
>
> Key: YARN-180
> URL: https://issues.apache.org/jira/browse/YARN-180
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 0.23.3
> Reporter: Thomas Graves
> Assignee: Arun C Murthy
> Priority: Critical
> Fix For: 2.0.3-alpha, 0.23.5
>
> Attachments: YARN-180.patch
>
>
> The capacity scheduler has the ability to 'reserve' containers.
> Unfortunately before it decides that it goes to reserved rather then
> assigned, the Container object is created which creates a container token
> that expires in roughly 10 minutes by default.
> This means that by the time the NM frees up enough space on that node for the
> container to move to assigned the container token may have expired.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
