[
https://issues.apache.org/jira/browse/YARN-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292548#comment-14292548
]
Hadoop QA commented on YARN-3098:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12694617/YARN-3098.1.patch
against trunk revision 21d5599.
{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.recovery.TestFSRMStateStore
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6422//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6422//console
This message is automatically generated.
> Create common QueueCapacities class in Capacity Scheduler to track
> capacities-by-labels of queues
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-3098
> URL: https://issues.apache.org/jira/browse/YARN-3098
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-3098.1.patch
>
>
> Similar to YARN-3092, after YARN-796, now queues (ParentQueue and LeafQueue)
> need to track capacities-label (e.g. absolute-capacity, maximum-capacity,
> absolute-capacity, absolute-maximum-capacity, etc.). It's better to have a
> class to encapsulate these capacities to make both better
> maintainability/readability and fine-grained locking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
