hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8664) Small fix ups for memory size outputs in UI
Date Sat, 08 Jun 2013 22:29:20 GMT

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

stack commented on HBASE-8664:
------------------------------

[~enis]

bq. Not sure this is better readable. Should we instead wrap humanReadablleInt to uppercase
K/M/G, and append B ourselves?

If we were going to go this route, I'd just do up our own humanReadableInt.

Mind if I commit this for time being?
                
> Small fix ups for memory size outputs in UI
> -------------------------------------------
>
>                 Key: HBASE-8664
>                 URL: https://issues.apache.org/jira/browse/HBASE-8664
>             Project: HBase
>          Issue Type: Bug
>          Components: UI
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.95.1
>
>         Attachments: ui.txt
>
>
> This issue goes in the 'polish' category.  On regionserver ui, we were listing raw bytes
for heap size, memstore size, etc.  I put in place StringUtils.humanReadableInt (looked to
see if bootstrap could do it for us but doesn't seem so, not w/o plugin).  I then made all
the megabytes and kilobytes match StringUtils.humanReadableInt with its 'm' instead of 'MB'
and 'k' instead of KB.  Removed a stray KB that was in the wrong place too.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message