[
https://issues.apache.org/jira/browse/HBASE-15722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junegunn Choi updated HBASE-15722:
----------------------------------
Resolution: Resolved
Status: Resolved (was: Patch Available)
I believe HBASE-20037 (by [~zhangduo]) effectively fixed the issue (although it
does not add the current WAL size to the metric as suggested in the patch
here), so let me close this. But please correct me if I'm missing anything.
I discovered the problem by examining the {{hlogFileSize}} metric on both an
HBase 1 cluster and an HBase 2 cluster. In the HBase 2 cluster, the metric
closely matched the actual file sizes, whereas in the HBase 1 cluster it
differed significantly.
> Size. WAL Files (bytes) in regionserver status page displays negative values
> ----------------------------------------------------------------------------
>
> Key: HBASE-15722
> URL: https://issues.apache.org/jira/browse/HBASE-15722
> Project: HBase
> Issue Type: Bug
> Components: UI
> Affects Versions: 2.0.0
> Reporter: Samir Ahmic
> Assignee: Samir Ahmic
> Priority: Minor
> Attachments: HBASE-15722_v0.patch, HBASE-15722_v1.patch,
> HBASE-15722_v2.patch, WALs.png
>
>
> Here is the line from ServerMetricTmpl.jamon
> {code}
> TraditionalBinaryPrefix.long2String(mWrap.getWALFileSize(), "B", 1)
> {code}
> I will change this to StringUtils.humanSize()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
