[
https://issues.apache.org/jira/browse/HBASE-29479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Connell updated HBASE-29479:
------------------------------------
Description: When asked for a QuotaLimiter for a given user, the QuotaCache
checks if that user's quota state is cached. If it is, it returns a
QuotaLimiter based on the cached information. If not, it returns a default
QuotaLimiter, (was: HBASE-29387 reduced the default interval between runs of
QuotaRefresherChore. This exposed an issue for RegionServers upon started.
Their quota caches contain incorrect information until QuotaRefresherChore,
which by default is not for 12 hours.
The logic of QuotaRefresherChore should be run immediately upon RegionServer
startup, and then every 12 hours after that.)
> QuotaCache is not populated until first run of QuotaRefresherChore
> ------------------------------------------------------------------
>
> Key: HBASE-29479
> URL: https://issues.apache.org/jira/browse/HBASE-29479
> Project: HBase
> Issue Type: Improvement
> Reporter: Charles Connell
> Assignee: Charles Connell
> Priority: Minor
> Labels: pull-request-available
>
> When asked for a QuotaLimiter for a given user, the QuotaCache checks if that
> user's quota state is cached. If it is, it returns a QuotaLimiter based on
> the cached information. If not, it returns a default QuotaLimiter,
--
This message was sent by Atlassian Jira
(v8.20.10#820010)