You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Charles Connell (Jira)" <ji...@apache.org> on 2025/09/12 15:14:00 UTC

[jira] [Resolved] (HBASE-29573) Fully load QuotaCache instead of reading individual rows on demand

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

Charles Connell resolved HBASE-29573.
-------------------------------------
    Fix Version/s: 2.7.0
                   3.0.0-beta-2
                   2.6.4
       Resolution: Fixed

> Fully load QuotaCache instead of reading individual rows on demand
> ------------------------------------------------------------------
>
>                 Key: HBASE-29573
>                 URL: https://issues.apache.org/jira/browse/HBASE-29573
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Charles Connell
>            Assignee: Charles Connell
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.7.0, 3.0.0-beta-2, 2.6.4
>
>
> I've found that HBASE-29479 will, in practice, increase load on the quota table quite a bit. While it achieved its goal of quota correctness, this increase in load is an unacceptable downside.
> In response, I'd like to find a way for QuotaCache to always serve correct quotas, and also keep load on the quota table low. There is a simple way to do this, which is to simply scan the entire table into memory at startup, again when quotas change, plus every refresh interval. This also simplifies the QuotaCache.



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