hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16677) Add table size (total store file size) to table page
Date Sun, 25 Sep 2016 07:32:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520383#comment-15520383
] 

Hudson commented on HBASE-16677:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #1669 (See [https://builds.apache.org/job/HBase-Trunk_matrix/1669/])
HBASE-16677 Add table size (total store file size) to table page (chenheng: rev f5351e2dbd29ab32dbd4044844feb6a94d9fea98)
* (edit) hbase-server/src/main/resources/hbase-webapps/master/table.jsp
Revert "HBASE-16677 Add table size (total store file size) to table (chenheng: rev b14fb14886686d3135f718ff7e067230ff7d62fc)
* (edit) hbase-server/src/main/resources/hbase-webapps/master/table.jsp
HBASE-16677 Add table size (total store file size) to table page (Guang (chenheng: rev f7bb6fbf21a6a86700b8411311343f0be80ebf3f)
* (edit) hbase-server/src/main/resources/hbase-webapps/master/table.jsp


> Add table size (total store file size) to table page
> ----------------------------------------------------
>
>                 Key: HBASE-16677
>                 URL: https://issues.apache.org/jira/browse/HBASE-16677
>             Project: HBase
>          Issue Type: New Feature
>          Components: website
>            Reporter: Guang Yang
>            Assignee: Guang Yang
>            Priority: Minor
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16677_v0.patch, HBASE-16677_v1.patch, HBASE-16677_v2.patch,
HBASE-16677_v3.patch, mini_cluster_master.png, prod_cluster_partial.png, table_page_v3.png
>
>
> Currently there is not an easy way to get the table size from the web UI, though we have
the region size on the page, it is still convenient to have a table for the table size stat.
> Another pain point is that when the table grow large with tens of thousands of regions,
it took extremely long time to load the page, however, sometimes we don't want to check all
the regions. An optimization could be to accept a query parameter to specify the number of
regions to render.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message