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

Enis Soztutar commented on HBASE-16677:
---------------------------------------

This seems useful. 

Do we actually stop rendering here? I did not see it. Have you tested with more 
than 10K regions? 
{code}
+    if (numRegionsRendered < numRegionsToRender) {
+      numRegionsRendered++; 
{code}

Please use {{TraditionalBinaryPrefix.long2String()}} instead of this: 
{code}
while (storeSize > 1024 && i < sizeUnits.length - 1)  {
+        storeSize /= 1024;
+        ++i;
+      }
{code}

Can we please change the param name from regions to numRegions, and also have a 
link in the warning message to the same page with the parameter set to render 
all regions. 

> 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
>            Priority: Minor
>         Attachments: HBASE-16677_v0.patch, HBASE-16677_v1.patch, 
> mini_cluster_master.png, prod_cluster_partial.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)

Reply via email to