Skip to content

HBASE-30348 Throttles should work for system tables (excluding quotas, meta, namespace) [branch-2] - #8785

Draft
rmdmattingly wants to merge 1 commit into
apache:branch-2from
HubSpot:HBASE-30348-v2-best-effort-branch-2
Draft

rmdmattingly wants to merge 1 commit into
apache:branch-2from
HubSpot:HBASE-30348-v2-best-effort-branch-2

Conversation

@rmdmattingly

Copy link
Copy Markdown
Contributor

Draft backport of #8774 to branch-2. It's open mainly to run CI on branch-2, since the first attempt at HBASE-30348 (#8591) deadlocked in tests here and was reverted.

The cherry-pick applied cleanly apart from one test import, HBaseTestingUtil → HBaseTestingUtility.

🤖 Generated with Claude Code

…, meta, namespace)

System tables outside the hbase namespace, such as the backup tables, can
generate a lot of IO but could never be throttled. Only hbase:meta,
hbase:quota and hbase:namespace remain exempt, because they are read while
the master is still initializing.

Throttling is now best effort: no request waits for the quota cache to load.
Until a load fully succeeds, requests get default quota state, which does not
throttle, and failed loads are retried. Waiting on the load inline is what
deadlocked master startup on branch-2 in the first attempt at this change,
since the load needs hbase:quota and the master.

Each refresh also reloads once more when it finds tables with new quotas.
Cluster scope table quotas are converted to machine scope using factors
computed before the fetch, so a newly limited table previously got the full
cluster limit on every RegionServer until the next refresh. Per-user table
quotas now get factors as well; before, only tables with a table quota did.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant