[
https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898192#comment-15898192
]
Wangda Tan commented on YARN-6164:
----------------------------------
Adding {{QueueConfigurations}} to QueueInfo is a good idea to me, but since it
is supposed to handle other options like capacity/preemption-disabled, etc. I
would prefer to continue existing approach of this patch, and think about how
to add QueueConfiguration separately.
In my opinion MaxAMPercentage is subject to be changed, so would prefer to make
it {{@Unstable/@Private}} for MaxAMPercentages.java (methods and class), and
QueueInfo#getMaxAMPercentages.
Thoughts?
> Expose maximum-am-resource-percent in YarnClient
> ------------------------------------------------
>
> Key: YARN-6164
> URL: https://issues.apache.org/jira/browse/YARN-6164
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.7.2
> Reporter: Benson Qiu
> Assignee: Benson Qiu
> Attachments: YARN-6164.001.patch, YARN-6164.002.patch,
> YARN-6164.003.patch, YARN-6164.004.patch, YARN-6164.005.patch
>
>
> `yarn.scheduler.capacity.maximum-am-resource-percent` is exposed through the
> [Cluster Scheduler
> API|http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API],
> but not through
> [YarnClient|https://hadoop.apache.org/docs/current/api/org/apache/hadoop/yarn/client/api/YarnClient.html].
> Since YarnClient and RM REST APIs depend on different ports (8032 vs 8088 by
> default), it would be nice to expose `maximum-am-resource-percent` in
> YarnClient as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
