You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/07/26 01:06:00 UTC

[jira] [Created] (HBASE-27241) Add metrics for evaluating cost and effectiveness of bloom filters

Bryan Beaudreault created HBASE-27241:
-----------------------------------------

             Summary: Add metrics for evaluating cost and effectiveness of bloom filters
                 Key: HBASE-27241
                 URL: https://issues.apache.org/jira/browse/HBASE-27241
             Project: HBase
          Issue Type: Improvement
            Reporter: Bryan Beaudreault
            Assignee: Bryan Beaudreault


Bloom filters can be costly for some tables, easily resulting in an aggregate memory footprint of many GBs. It's currently hard to monitor for that cost on a per-table basis. You can view {{staticBloomSize}} in JMX, but that is for the whole server. Otherwise you must manually sum the values using the regionserver UI.  We can add this (as well as staticIndexSize) to the per-table metrics.

Additionally, it can be hard to know how effective those bloom filters are. I think the easiest way to measure that is to count bloomFilterRequests and bloomFilterNegativeResults. With these metrics in hand, one can have an easier time deciding how much memory they want to give to their L1 cache and/or whether they want to disable blooms on a table.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)