[
https://issues.apache.org/jira/browse/YARN-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066741#comment-14066741
]
Hadoop QA commented on YARN-2008:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12656545/YARN-2008.2.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 1 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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4363//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4363//console
This message is automatically generated.
> CapacityScheduler may report incorrect queueMaxCap if there is hierarchy
> queue structure
> -----------------------------------------------------------------------------------------
>
> Key: YARN-2008
> URL: https://issues.apache.org/jira/browse/YARN-2008
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.3.0
> Reporter: Chen He
> Assignee: Chen He
> Attachments: YARN-2008.1.patch, YARN-2008.2.patch
>
>
> If there are two queues, both allowed to use 100% of the actual resources in
> the cluster. Q1 and Q2 currently use 50% of actual cluster's resources and
> there is not actual space available. If we use current method to get
> headroom, CapacityScheduler thinks there are still available resources for
> users in Q1 but they have been used by Q2.
> If the CapacityScheduelr has a hierarchy queue structure, it may report
> incorrect queueMaxCap. Here is a example
> || ||rootQueue|| ||
> | | / |
> \ |
> | L1ParentQueue1 | |
> L1ParentQueue2 |
> | (allowed to use up 80% of its parent) | | (allowed to use 20%
> in minimum of its parent)|
> | / | \ | |
> | L2LeafQueue1 | L2LeafQueue2 | |
> |(50% of its parent) | (50% of its parent in minimum) | |
> When we calculate headroom of a user in L2LeafQueue2, current method will
> think L2LeafQueue2 can use 40% (80%*50%) of actual rootQueue resources.
> However, without checking L1ParentQueue1, we are not sure. It is possible
> that L1ParentQueue2 have used 40% of rootQueue resources right now. Actually,
> L2LeafQueue2 can only use 30% (60%*50%).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
