[
https://issues.apache.org/jira/browse/HBASE-15640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254203#comment-15254203
]
Hudson commented on HBASE-15640:
--------------------------------
FAILURE: Integrated in HBase-0.98-matrix #335 (See
[https://builds.apache.org/job/HBase-0.98-matrix/335/])
HBASE-15640 L1 cache doesn't give fair warning that it is showing (apurtell:
rev 906841a886f0bd12c0e0c2b328f6b4b9be7f6f38)
* hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileReaderV2.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
*
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
> L1 cache doesn't give fair warning that it is showing partial stats only when
> it hits limit
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-15640
> URL: https://issues.apache.org/jira/browse/HBASE-15640
> Project: HBase
> Issue Type: Sub-task
> Components: BlockCache
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0, 1.2.2
>
> Attachments: 15640.patch, Screen Shot 2016-04-12 at 4.21.50 PM.png,
> bc.ui (1).patch, bc.ui.patch, bc.ui.v3.patch
>
>
> I was baffled looking at L1 Cache because it was stuck at 100k blocks and
> only 'loading' 3G of data according to the UI. When I looked in log, all the
> numbers looked write in the Cache summary reported in log.
> Turns out our buckecache UI template will cut off calculating stats at a
> limit --which is probably what we want -- but the fact that it has done this
> should be more plain.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
