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 B0750200CD6 for ; Mon, 31 Jul 2017 14:04:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AED65165201; Mon, 31 Jul 2017 12:04:06 +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 01292165200 for ; Mon, 31 Jul 2017 14:04:05 +0200 (CEST) Received: (qmail 48007 invoked by uid 500); 31 Jul 2017 12:04:05 -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 47984 invoked by uid 99); 31 Jul 2017 12:04:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jul 2017 12:04:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 00EF6C028C for ; Mon, 31 Jul 2017 12:04:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 34RuQKoY2Uyk for ; Mon, 31 Jul 2017 12:04:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C6C655F56C for ; Mon, 31 Jul 2017 12:04:00 +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 66CC0E0996 for ; Mon, 31 Jul 2017 12:04:00 +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 1E73B2464E for ; Mon, 31 Jul 2017 12:04:00 +0000 (UTC) Date: Mon, 31 Jul 2017 12:04:00 +0000 (UTC) From: "Naganarasimha G R (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6898) RM node labels page should display total used resources of each label. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 31 Jul 2017 12:04:06 -0000 [ https://issues.apache.org/jira/browse/YARN-6898?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16107= 213#comment-16107213 ]=20 Naganarasimha G R commented on YARN-6898: ----------------------------------------- [~daemon], bq. Another question is what I should do for this next? Waiting for the new= UI or continue the work of this JIRA? Well IMO its not a must have feature as its already available in the existi= ng Scheduler page and at the same time new UI plans to provide better visua= lizations of the same, so i am +0 on this.=20 If [~sunilg] or you have more valid reasons then would like hear it. > RM node labels page should display total used resources of each label. > ---------------------------------------------------------------------- > > Key: YARN-6898 > URL: https://issues.apache.org/jira/browse/YARN-6898 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler > Reporter: YunFan Zhou > Assignee: YunFan Zhou > > The RM node labels page only show *Label Name*=E3=80=81*Label Type*=E3=80= =81*Num Of Active NMs*=E3=80=81*Total Resource* > information of each node label, but there isn't any place for us to see t= he total used resource of the node label. > The total used resource of the node label is very important, because we c= an use it to check the overall load for this > label. We will implement it. Any suggestion? -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org