[
https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953457#comment-14953457
]
Wangda Tan commented on YARN-3216:
----------------------------------
bq. now queueResourceLimitsInfo.getQueueCurrentLimit() is common per queue. And
a queue may have 2 or 3 accessible-labels. So I feel I may not be able to use
this total value always like in getAMResourceLimit. Hence I think I need to
calculate max-capacity based on label-percentage per-queue. How do you feel?
You can take a look at {{AbstractCSQueue#getCurrentLimitResource}} as an
example to see how queue calculates max-capacity by partition.
> Max-AM-Resource-Percentage should respect node labels
> -----------------------------------------------------
>
> Key: YARN-3216
> URL: https://issues.apache.org/jira/browse/YARN-3216
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Wangda Tan
> Assignee: Sunil G
> Priority: Critical
> Attachments: 0001-YARN-3216.patch, 0002-YARN-3216.patch,
> 0003-YARN-3216.patch, 0004-YARN-3216.patch, 0005-YARN-3216.patch
>
>
> Currently, max-am-resource-percentage considers default_partition only. When
> a queue can access multiple partitions, we should be able to compute
> max-am-resource-percentage based on that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
