You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/09/07 19:17:46 UTC
[jira] [Updated] (YARN-3124) Capacity Scheduler
LeafQueue/ParentQueue should use QueueCapacities to track
capacities-by-label
[ https://issues.apache.org/jira/browse/YARN-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated YARN-3124:
------------------------------------------
Labels: 2.6.1-candidate (was: )
Fix Version/s: 2.6.1
Pulled this into 2.6.1 as a dependency. Had to fix merge conflicts and make minor changes to get it to work on 2.6.1.
Ran all ResourceManager tests before pushing this in.
> Capacity Scheduler LeafQueue/ParentQueue should use QueueCapacities to track capacities-by-label
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-3124
> URL: https://issues.apache.org/jira/browse/YARN-3124
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, client, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Labels: 2.6.1-candidate
> Fix For: 2.7.0, 2.6.1
>
> Attachments: YARN-3124.1.patch, YARN-3124.2.patch, YARN-3124.3.patch, YARN-3124.4.patch, YARN-3124.5.patch
>
>
> After YARN-3098, capacities-by-label (include used-capacity/maximum-capacity/absolute-maximum-capacity, etc.) should be tracked in QueueCapacities.
> This patch is targeting to make capacities-by-label in CS Queues are all tracked by QueueCapacities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)