[
https://issues.apache.org/jira/browse/HBASE-27800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault resolved HBASE-27800.
---------------------------------------
Fix Version/s: 2.6.0
3.0.0-beta-2
Release Note: Adds a bunch of new configs for default user machine quotas:
hbase.quota.default.user.machine.read.num,
hbase.quota.default.user.machine.read.size,
hbase.quota.default.user.machine.write.num,
hbase.quota.default.user.machine.write.size,
hbase.quota.default.user.machine.request.num,
hbase.quota.default.user.machine.request.size. Setting any these will apply the
given limit as a default for users which are not explicitly covered by existing
quotas defined through set_quota, etc.
Resolution: Fixed
> Add support for default user quotas using USER => 'all'
> --------------------------------------------------------
>
> Key: HBASE-27800
> URL: https://issues.apache.org/jira/browse/HBASE-27800
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Ray Mattingly
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.0, 3.0.0-beta-2
>
>
> If someone sets a quota with USER => 'all' (or maybe '*'), treat that as a
> default quota for each individual user. When a request comes from a user, it
> will lookup current QuotaState based on username. If one doesn't exist, it
> will be pre-filled with whatever the 'all' quota was set to. Otherwise, if
> you then define a quota for a specific user that will override whatever
> default you have set for that user only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
