[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888474#comment-15888474
]
churro morales commented on YARN-6164:
--------------------------------------
This looks like a new feature, what do you think about putting this in a separate ticket so
we can work on this in parallel. Also what do you think about getting the existing work in?
I could use this patch where I work as well.
Thanks everyone.
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org
|