hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17774) Improve locality info in table details page
Date Tue, 14 Mar 2017 03:26:41 GMT

    [ 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

View raw message