[
https://issues.apache.org/jira/browse/HBASE-15640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15640:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.2.2
1.4.0
1.3.0
2.0.0
Release Note:
The blockcache UI tab would stop refreshing at 100k blocks (configurable, see
"hbase.ui.blockcache.by.file.max"), which isn't very many blocks when doing a
big cache, giving a misleading picture of the content of L1 and/or L2 cache. Up
the default limit to 1M blocks (UI takes a while but just a few seconds
counting over 1M blocks).
Also, when beyond the limit give the user a noticeable WARNING in the UI.
Status: Resolved (was: Patch Available)
> 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, 1.4.0, 1.2.2
>
> Attachments: 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)
