[
https://issues.apache.org/jira/browse/HBASE-30348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-30348:
-------------------------------
At least this breaks branch-2.x, it introduces dead lock on namespace table
initialization and quota table initialization. As in TableNamespaceManager, we
will do a table.get on namespace table to make sure that it is online, but
proceeding other initialization work such as creating the hbase:quota table.
But when doing table.get on namespace table, we will fail because when checking
quota, the quota manager will fail because hbase:quota table is not created yet.
I'm going to revert this on branch-2.x, and I strongly suggest that we also
review the implementation on master branch-3.x to make sure that it does not
introduce other dead lock issues.
Thanks.
> 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)
