Hadoop QA commented on YARN-3356:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision c239b6d.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:green}+1 tests included{color}.  The patch appears to include 6 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 

    {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 


Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7018//console

This message is automatically generated.

> Capacity Scheduler FiCaSchedulerApp should use ResourceUsage to track 
> used-resources-by-label.
> ----------------------------------------------------------------------------------------------
>                 Key: YARN-3356
>                 URL: https://issues.apache.org/jira/browse/YARN-3356
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-3356.1.patch, YARN-3356.2.patch, YARN-3356.3.patch, 
> YARN-3356.4.patch
> Simliar to YARN-3099, Capacity Scheduler's LeafQueue.User/FiCaSchedulerApp 
> should use ResourceRequest to track resource-usage/pending by label for 
> better resource tracking and preemption. 
> And also, when application's pending resource changed (container allocated, 
> app completed, moved, etc.), we need update ResourceUsage of queue 
> hierarchies.

This message was sent by Atlassian JIRA

Reply via email to