[jira] [Updated] (YARN-3098) Create common QueueCapacities class in Capacity Scheduler to track capacities-by-labels of queues

["Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated YARN-3098:
------------------------------------------
           Labels: 2.6.1-candidate  (was: )
    Fix Version/s: 2.6.1

Pulled this into 2.6.1 as a dependency. Applies cleanly. Had to change {{(float) method.invoke(obj);}} to {{(Float) method.invoke(obj);}} for Java 6 in TestQueueCapacities.java

Ran all ResourceManager tests before pushing this in.


> 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
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0, 2.6.1
>
>         Attachments: YARN-3098.1.patch, YARN-3098.2.patch, YARN-3098.3.patch, YARN-3098.4.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)