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 29A85102F4 for ; Thu, 19 Mar 2015 03:47:39 +0000 (UTC) Received: (qmail 85793 invoked by uid 500); 19 Mar 2015 03:47:38 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 85609 invoked by uid 500); 19 Mar 2015 03:47:38 -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 85298 invoked by uid 99); 19 Mar 2015 03:47:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2015 03:47:38 +0000 Date: Thu, 19 Mar 2015 03:47:38 +0000 (UTC) From: "Naganarasimha G R (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI 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-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368463#comment-14368463 ] Naganarasimha G R commented on YARN-3362: ----------------------------------------- Thanks [~wangda], Regarding the approach to display i had few concerns : * There will be some common queue metrics across the labels, wont it get repeated across for each label if a queue is mapped to multiple labels ? * IIUC most of the queue Metrics might not be specific to a label, like Capacity, Absolute max capacity, Max apps, Max AM's per user etc... . Correct me if my understanding on this is wrong. * Apart from the label specific queue metrics like (label capacity, label abs capacity,used) are there any new Label specific queue metrics you have in your mind ? * would it be better to list like {noformat} + root [=====================] 30% used + a [=======================================] 75% used + a1 [=================] 30% used --------------------------------------------- | Queue Metrics | |--------------------------------------------| | metrics1 | value1 | | metrics2 | value2 | --------------------------------------------- | Active Users info (yarn-3273) | |--------------------------------------------| | user1 | info | | user2 | info | --------------------------------------------- | Label Resource usage info | |--------------------------------------------| | label_x [=====================] 30% used | | label_y [================] 20% used | ---------------------------------------------- + a2 [=================] 30% used ... {noformat} * Also if required we can have seperate page (/in the labels page/append at the end of CS page) like : {noformat} + label_x [=====================] 30% used [Actual Resource - Used resource ] + root [=====================] 30% used [Actual Resource - Used resource ] + a [=======================================] 75% used [Actual Resource - Used resource ] + a1 [=================] 30% used [Actual Resource - Used resource ] + label_y + root [...] + ... + label_z + root [...] {noformat} YARN-3273, has added more info to the CS page so we need to consider the size of page and its usability. Please provide your thoughts on the same > Add node label usage in RM CapacityScheduler web UI > --------------------------------------------------- > > Key: YARN-3362 > URL: https://issues.apache.org/jira/browse/YARN-3362 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler, resourcemanager, webapp > Reporter: Wangda Tan > Assignee: Naganarasimha G R > > We don't have node label usage in RM CapacityScheduler web UI now, without this, user will be hard to understand what happened to nodes have labels assign to it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)