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 A73CC200C3F for ; Wed, 8 Mar 2017 03:59:44 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A5C37160B74; Wed, 8 Mar 2017 02:59:44 +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 EBC0D160B68 for ; Wed, 8 Mar 2017 03:59:43 +0100 (CET) Received: (qmail 20679 invoked by uid 500); 8 Mar 2017 02:59:43 -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 20668 invoked by uid 99); 8 Mar 2017 02:59:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Mar 2017 02:59:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id AD6F5C3251 for ; Wed, 8 Mar 2017 02:59:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 51EKR-k2TGCV for ; Wed, 8 Mar 2017 02:59:42 +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 846325F1EE for ; Wed, 8 Mar 2017 02:59:41 +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 A4F56E086A for ; Wed, 8 Mar 2017 02:59:38 +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 0310424176 for ; Wed, 8 Mar 2017 02:59:38 +0000 (UTC) Date: Wed, 8 Mar 2017 02:59:38 +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: Wed, 08 Mar 2017 02:59:44 -0000 [ https://issues.apache.org/jira/browse/YARN-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900609#comment-15900609 ] Sunil G commented on YARN-6164: ------------------------------- Hi [~benson.qiu] I had offline discussed with [~leftnoteasy] yesterday and we feel that we can have a class named {{QueueCapacities}} in {{QueueInfo}}. This could have fields like cap/max-cap/max-am-perc (all are per label based) etc. Could you please share your thoughts also? > 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