Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB51417F80 for ; Wed, 25 Nov 2015 06:08:11 +0000 (UTC) Received: (qmail 6717 invoked by uid 500); 25 Nov 2015 06:08:11 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 6657 invoked by uid 500); 25 Nov 2015 06:08:11 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 6362 invoked by uid 99); 25 Nov 2015 06:08:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2015 06:08:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1C40C2C1F76 for ; Wed, 25 Nov 2015 06:08:11 +0000 (UTC) Date: Wed, 25 Nov 2015 06:08:11 +0000 (UTC) From: "Naganarasimha G R (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026266#comment-15026266 ] Naganarasimha G R commented on YARN-4304: ----------------------------------------- Hi [~sunilg], bq. As needed I feel it can be handled in new ticket since 4162 is committed. No issues in working on new jira but my only intention is to get the REST o/p corrected ppl need to get 2 jira's merged and YARN-4162 was recently merged and not gone into any versions. But anyway first lets gets [~wangda]'s thoughts on this. bq. Yes. I have used directly. I think as we have encapsulated class, I will make changes. Reason being that the objects in xml come one after the other and is not so readable. I was referring to the changes in {{CapacitySchedulerLeafQueueInfo}} Also check how better we can restructure the new class {{PartitionResourceInfo}} or resuse the existing classes like {{PartitionResourceUsageInfo}} introduced in YARN-4162 > AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics > ---------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-4304 > URL: https://issues.apache.org/jira/browse/YARN-4304 > Project: Hadoop YARN > Issue Type: Sub-task > Components: webapp > Affects Versions: 2.7.1 > Reporter: Sunil G > Assignee: Sunil G > Attachments: 0001-YARN-4304.patch, 0002-YARN-4304.patch, 0003-YARN-4304.patch, REST_and_UI.zip > > > As we are supporting per-partition level max AM resource percentage configuration, UI and various metrics also need to display correct configurations related to same. > For eg: Current UI still shows am-resource percentage per queue level. This is to be updated correctly when label config is used. > - Display max-am-percentage per-partition in Scheduler UI (label also) and in ClusterMetrics page > - Update queue/partition related metrics w.r.t per-partition am-resource-percentage -- This message was sent by Atlassian JIRA (v6.3.4#6332)