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

Hadoop QA commented on HBASE-13581:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} 
| {color:red} HBASE-13581 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.2.1/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12731131/HBASE-13581.patch |
| JIRA Issue | HBASE-13581 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/2737/console |
| Powered by | Apache Yetus 0.2.1   http://yetus.apache.org |


This message was automatically generated.



> Improve usability for storefile stats in web status pages
> ---------------------------------------------------------
>
>                 Key: HBASE-13581
>                 URL: https://issues.apache.org/jira/browse/HBASE-13581
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>    Affects Versions: 1.0.0
>            Reporter: Sean Busbey
>            Assignee: Ashutosh Jindal
>            Priority: Minor
>              Labels: beginner
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13581.patch, rs_in_master_status_page.tiff
>
>
> Right now the "Storefiles" section of the Region Servers status shown in the 
> Master web ui is inconsistent in units (sometimes "m" and sometimes "mb") and 
> uses units that are fixed rather than adapting to the number being presented 
> (e.g. reporting a bloom filter size of 13540k instead of 13m).
> Clean up to
> * consistently use correct units (i.e. KiB, MiB, GiB since that's what we're 
> measuring)
> * adapt the units used so that we use the biggest ones



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

Reply via email to