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 568C3200C45 for ; Tue, 14 Mar 2017 04:26:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 552F3160B85; Tue, 14 Mar 2017 03:26:46 +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 A0380160B5D for ; Tue, 14 Mar 2017 04:26:45 +0100 (CET) Received: (qmail 21794 invoked by uid 500); 14 Mar 2017 03:26:44 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 21773 invoked by uid 99); 14 Mar 2017 03:26:44 -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; Tue, 14 Mar 2017 03:26:44 +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 109D2C036E for ; Tue, 14 Mar 2017 03:26:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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-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 31AX3EcwI4Ip for ; Tue, 14 Mar 2017 03:26:43 +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 EE6ED5FC06 for ; Tue, 14 Mar 2017 03:26:42 +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 08BDAE04A6 for ; Tue, 14 Mar 2017 03:26:41 +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 A4C6D243A8 for ; Tue, 14 Mar 2017 03:26:41 +0000 (UTC) Date: Tue, 14 Mar 2017 03:26:41 +0000 (UTC) From: "Yu Li (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17774) Improve locality info in table details page MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 14 Mar 2017 03:26:46 -0000 [ https://issues.apache.org/jira/browse/HBASE-17774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923484#comment-15923484 ] Yu Li commented on HBASE-17774: ------------------------------- It seems to me the below parts are still preferable even with HBASE-15675: * Hide locality "0.0" if the stores are all empty, i.e. no store file is present. * Summary of the locality, or say the overall locality And other parts seems to be perfectly covered (smile). > Improve locality info in table details page > ------------------------------------------- > > Key: HBASE-17774 > URL: https://issues.apache.org/jira/browse/HBASE-17774 > Project: HBase > Issue Type: Improvement > Components: UI > Affects Versions: 1.3.0 > Reporter: Lars George > > The {{table.jsp}} page does list the locality info of each region, but is missing some vital other details, which are: > - An extra column listing store and store file counts (could be two separate columns too like in Master and RS UI, but a single column saves space, for example "3/6", meaning three stores and six store files in total > - Hide locality "0.0" if the stores are all empty, i.e. no store file is present. It makes little sense penalizing an empty store when it comes to the total locality of the table. > - Make region name clickable like on RS status page, linking to {{region.jsp}} page showing store details. > - Summary row at the end, showing the total locality (see note above), number stores, number of store files. That is, compute the _real_ locality, which is considering only the actual store files. > I also wish we had some simple but effective charts/diagrams here, like a heatmap for data distribution within the table (since we have all of this info), or another heatmap for current request distribution. Strong +1 to add that here too. > I have reasoned about this at customers way too often to not have this improved somehow. For the enterprise level admin, a good UI goes a long way! -- This message was sent by Atlassian JIRA (v6.3.15#6346)