[ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869435#comment-15869435 ]
Sunil G commented on YARN-6164: ------------------------------- [~bibinchundatt], I am still doubtful about that approach. Since many informations related to configuration is already exposed by QueueInfo, *Properties* may not a become a better logical grouping unless we move all existing config items to new subclass. This will cause compatibility, and we wont be able to do that. For me, I feel we many confuse more if we add *Properties* sub section , as its not a single grouping for configuration related items. > 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.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