[
https://issues.apache.org/jira/browse/HBASE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680865#comment-13680865
]
Hudson commented on HBASE-8664:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #564 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/564/])
HBASE-8664 Small fix ups for memory size outputs in UI (Revision 1491902)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/master/RegionServerListTmpl.jamon
*
/hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/RegionListTmpl.jamon
*
/hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/ServerMetricsTmpl.jamon
> 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.98.0, 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
