hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-8370) Report data block cache hit rates apart from aggregate cache hit rates
Date Tue, 22 Jul 2014 04:38:39 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-8370.
--------------------------

    Resolution: Implemented

Resolving as implemented (after I commit HBASE-11559).  Varun can get his block reporting
by type by looking at UI/JSON report (dumping out over a period if wants to study production
a while) and Elliott gets his way with no extra metrics added reporting by type.

> Report data block cache hit rates apart from aggregate cache hit rates
> ----------------------------------------------------------------------
>
>                 Key: HBASE-8370
>                 URL: https://issues.apache.org/jira/browse/HBASE-8370
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics
>            Reporter: Varun Sharma
>            Assignee: Varun Sharma
>            Priority: Minor
>
> Attaching from mail to dev@hbase.apache.org
> I am wondering whether the HBase cachingHitRatio metrics that the region server UI shows,
can get me a break down by data blocks. I always see this number to be very high and that
could be exagerated by the fact that each lookup hits the index blocks and bloom filter blocks
in the block cache before retrieving the data block. This could be artificially bloating up
the cache hit ratio.
> Assuming the above is correct, do we already have a cache hit ratio for data blocks alone
which is more obscure ? If not, my sense is that it would be pretty valuable to add one.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message