Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C1507200C29 for ; Tue, 28 Feb 2017 18:28:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BFCD4160B7C; Tue, 28 Feb 2017 17:28:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15C6D160B59 for ; Tue, 28 Feb 2017 18:28:51 +0100 (CET) Received: (qmail 10686 invoked by uid 500); 28 Feb 2017 17:28:51 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 10670 invoked by uid 99); 28 Feb 2017 17:28:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Feb 2017 17:28:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CC4C918E122 for ; Tue, 28 Feb 2017 17:28:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eKtKVD8vVQkH for ; Tue, 28 Feb 2017 17:28:50 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AB08B5F645 for ; Tue, 28 Feb 2017 17:28:49 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 98469E060F for ; Tue, 28 Feb 2017 17:28:46 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9A22024178 for ; Tue, 28 Feb 2017 17:28:45 +0000 (UTC) Date: Tue, 28 Feb 2017 17:28:45 +0000 (UTC) From: "Sunil G (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Feb 2017 17:28:52 -0000 [ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888503#comment-15888503 ] Sunil G commented on YARN-6164: ------------------------------- [~churromorales] I understood the your point. However this is an api exposed to client side and it ll be better if we do it clean. Otherwise once its released, we have to support the same for future version till we can deprecate it with a major version. The change suggested here is not very major, rather {{QueueConfigurations}} will be similar to {{MaxAMPercentage}} class in the patch. It should be pretty straight forward as per me. > 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