[
https://issues.apache.org/jira/browse/HBASE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4089:
-------------------------
Attachment: 4089.wip.txt
wip
Make BlockCaches Iterable.
Make it so can ask BlockCache if it has sub BlockCaches.
Add tools that can do sums, report block types, and age histograms when passed
block cache Iterators. Currently we report by file.
Removed the unused BlockCacheColumnFamilySummary stuff.
Made BlockPriority class since priority was in BucketCache and LruBlockCache.
TODO: Build out cache stats so report by slab for SlabCache and by bucket for
BucketCache.
TODO: See if I can remove the hokey reporting thread that dumps into the logs
every 5minutes the block cache 'status'.... see if can make data available via
metrics and elsewise (Currently we launch a thread to report but logging is at
DEBUG level so thread does nothing).
TODO: add a few web pages to report this stuff on.
Renamed CachedBlock as LruCachedBlock and then added new Interface CachedBlock
that has info common to all BlockCache implementaitons.
Renamed CachedBlockQueue as LruCachedBlockQueue
> blockCache contents report
> --------------------------
>
> Key: HBASE-4089
> URL: https://issues.apache.org/jira/browse/HBASE-4089
> Project: HBase
> Issue Type: New Feature
> Reporter: Doug Meil
> Assignee: Doug Meil
> Attachments: 4089.wip.txt, hbase_4089_blockcachereport.pdf,
> java_blockcache_checkpoint_2011_08_11.patch
>
>
> Summarized block-cache report for a RegionServer would be helpful. For
> example ...
> table1
> cf1 100 blocks, totalBytes=yyyyy, averageTimeInCache=XXXX hours
> cf2 200 blocks, totalBytes=zzzzz, averageTimeInCache=XXXX hours
> table2
> cf1 75 blocks, totalBytes=yyyyy, averageTimeInCache=XXXX hours
> cf2 150 blocks, totalBytes=zzzzz, averageTimeInCache=XXXX hours
> ... Etc.
> The current metrics list blockCacheSize and blockCacheFree, but there is no
> way to know what's in there. Any single block isn't really important, but
> the patterns of what CF/Table they came from, how big are they, and how long
> (on average) they've been in the cache, are important.
> No such interface exists in HRegionInterface. But I think it would be
> helpful from an operational perspective.
> Updated (7-29): Removing suggestion for UI. I would be happy just to get
> this report on a configured interval dumped to a log file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
