Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 7 Mar 2017 07:53:33 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13041511.1486591915000.16948.1488873213028@Atlassian.JIRA>
In-Reply-To: <JIRA.13041511.1486591915000@Atlassian.JIRA>
References: <JIRA.13041511.1486591915000@Atlassian.JIRA> <JIRA.13041511.1486591915054@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6164) Expose maximum-am-resource-percent
 in YarnClient
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Mar 2017 07:53:41 -0000


    [ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898896#comment-15898896 ] 

Sunil G commented on YARN-6164:
-------------------------------

Thanks [~leftnoteasy] for sharing the thoughts.

It makes sense by seeing the diversity of params we have in QueueInfo. On the same note in long run, we are looking for something like {{QueueCapacities}}, {{QueueConfigurations}}, and {{ResourceUsages}} inside *QueueInfo*. Correct? and {{MaxAMPercentage}} could be part of {{QueueCapacities}} itself.

I guess this could generalized improvement task, and for simplicity we could use *@Unstable/@Private* version of am percentage. Do you see this as a fine approach at this point?


> 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