[
https://issues.apache.org/jira/browse/HBASE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244822#comment-13244822
]
Enis Soztutar commented on HBASE-5601:
--------------------------------------
I have started working on this (and other per-table-cf metrics), but soon
realized that some of the changes require breaking compatibility with (soon to
be released) 0.94 in terms of metric names. So I decided to list the proposed
changes first to see whether we can come up with a plan.
As you know, HBASE-4219 and others added per-cf metrics, but there are a couple
of things we can improve on that (great) work. Some ideas I have:
- Make Per-cf and global block cache metrics naming consistent
(hbase.regionserver.blockCacheHitCount vs
hbase.RegionServerDynamicStatistics.tbl.usertable.cf.ycsb.bt.Data.fsBlockReadCacheHitCnt)
- Rename hbase.RegionServerDynamicStatistics.XXX -> hbase.regionserver.dyn.XXX
- Rename dynamic metric names
tbl.usertable.cf.ycsb.bt.Data.fsBlockReadCacheHitCnt ->
tbl=usertable.cf=ycsb.bt=Data.at=scan.BlockCacheHitCount. Here at stands for
access type, and can be scan or compaction.
- For at=compaction, we probably do not need per-block type (Data, Index, ...)
metric values, shall we aggregate them?
- Shall we extend per-cf metrics into HBASE-5533 (read/write latency
histograms)?
- With slab cache, we may no longer have one global block cache. Shall we
enable per-cache type metrics? This can imply renaming
hbase.regionserver.blockCache => hbase.regionserver.lrublockcache,
slabblockcache, etc.
- Add a configuration for disabling per-cf metrics.
- Thoughts ?
> Add per-column-family data block cache hit ratios
> -------------------------------------------------
>
> Key: HBASE-5601
> URL: https://issues.apache.org/jira/browse/HBASE-5601
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
>
> In addition to the overall block cache hit ratio it would be extremely useful
> to have per-column-family data block cache hit ratio metrics.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
