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 676E7200CF3 for ; Tue, 29 Aug 2017 19:24:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6595A167317; Tue, 29 Aug 2017 17:24: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 AFE05167315 for ; Tue, 29 Aug 2017 19:24:05 +0200 (CEST) Received: (qmail 98303 invoked by uid 500); 29 Aug 2017 17:24:04 -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 98014 invoked by uid 99); 29 Aug 2017 17:24:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Aug 2017 17:24:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 52F7F1A15F4 for ; Tue, 29 Aug 2017 17:24:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id HJ-YPzyEdbj2 for ; Tue, 29 Aug 2017 17:24:03 +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 4B5C660EE9 for ; Tue, 29 Aug 2017 17:24:03 +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 54C66E0E29 for ; Tue, 29 Aug 2017 17:24:01 +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 464D324158 for ; Tue, 29 Aug 2017 17:24:00 +0000 (UTC) Date: Tue, 29 Aug 2017 17:24:00 +0000 (UTC) From: "Daniel Templeton (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7071) Add vcores and number of containers in web UI v2 node heat map MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 29 Aug 2017 17:24:06 -0000 [ https://issues.apache.org/jira/browse/YARN-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145728#comment-16145728 ] Daniel Templeton commented on YARN-7071: ---------------------------------------- You are entirely correct, but what I've seen is that the vast majority of containers are the same: 1GB, 1 vcore. Even when they're not, it still doesn't hurt to have the information. Especially when the other two views show CPU and memory, so user's can get a more absolute picture. > Add vcores and number of containers in web UI v2 node heat map > -------------------------------------------------------------- > > Key: YARN-7071 > URL: https://issues.apache.org/jira/browse/YARN-7071 > Project: Hadoop YARN > Issue Type: Improvement > Components: yarn-ui-v2 > Affects Versions: 3.0.0-alpha4 > Reporter: Abdullah Yousufi > Assignee: Abdullah Yousufi > Attachments: Screen Shot 2017-08-29 at 7.42.26 PM.png, YARN-7071.001.patch > > > Currently, the node heat map displays memory usage per node. This change would add a dropdown to view cpu vcores or number of containers as well. -- 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