[ 
https://issues.apache.org/jira/browse/YARN-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317126#comment-14317126
 ] 

Jian He commented on YARN-3124:
-------------------------------

remove unused QueueCapacities#reinitialize
AbstractCSQueue#setupCapacities -> setupConfiguredCapacities
{{so we shouldn't do this for reservation queue }}, mind clarifying more?
minor format
{code}
    super.setupQueueConfigs(clusterResource);
   StringBuilder aclsString = new StringBuilder();
  public synchronized void reinitialize(
      CSQueue newlyParsedQueue, Resource clusterResource)
  throws IOException {
{code}

> 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
>         Attachments: YARN-3124.1.patch, YARN-3124.2.patch, YARN-3124.3.patch, 
> YARN-3124.4.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)

Reply via email to