[
https://issues.apache.org/jira/browse/HBASE-30348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18110669#comment-18110669
]
Ray Mattingly commented on HBASE-30348:
---------------------------------------
Because the hbase:namespace table is vestigial on 3.x, I believe the branch-3
backport is _almost_ safe. But, not quite, because it will be a problem in a
2.x to 3.x upgrade. I'm going to revert more broadly, and then start over on a
fix that's foolproof for 2.x.
[~zhangduo] do you have any preferences on how to change course in the new fix?
I wonder whether it's as simple as having the quota path suppress any failures
when the master isn't initialized, which would eliminate this class of deadlock
and allow us to support quotas on meta systems quite flexibly. Alternatively,
we could just selectively allow quotas for backup system tables, but that would
leave this deadlock potential in the code.
> Throttles should work for system tables (excluding quotas, meta)
> ----------------------------------------------------------------
>
> Key: HBASE-30348
> URL: https://issues.apache.org/jira/browse/HBASE-30348
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.6.7
> Reporter: Ray Mattingly
> Assignee: Ray Mattingly
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.1.0, 3.0.1, 2.6.8
>
>
> Right now throttles silently no-op for all system tables. Outside of the
> quotas table itself, of course, and perhaps the meta table I don't think this
> actually makes sense. We saw a pathologic build up of huge cells in
> incremental backups tables, for example, and it resulted in significant IO
> hotspots throughout our HBase clusters during backups and during bulk loads.
> We will fix that backups bug separately, but we would also love to have
> throttles in place on these backup system tables.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
