[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953496#comment-14953496 ]
Sunil G commented on YARN-3216: ------------------------------- Hi [~leftnoteasy] Thank you for confirming to use max-capacity also while calculating max-am-resource per-partition. Yes, {{getCurrentLimitResource}} shows the way how we can get the per-partition level max-capacity in a queue, I will be using the same only. Also TestApplicationLimits is not correct. It statically calculates full cluster resource as queue limit. I will correct that also in the next patch. > 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)