[
https://issues.apache.org/jira/browse/HBASE-21820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777557#comment-16777557
]
Xu Cang commented on HBASE-21820:
---------------------------------
thanks for the explanation!
I see what you two meant now. [~Yi Mei] is basically exposing a new interface
to admin to set quotas.
I was thinking what's the roadmap of resource management and how does this
interact with rsgroup quota, namespace quota, and rcu/wcu that [~Yi Mei]
implemented. But seems like this JIRA is not changing anything regarding that.
Thank you again. Best,
> Implement CLUSTER quota scope
> -----------------------------
>
> Key: HBASE-21820
> URL: https://issues.apache.org/jira/browse/HBASE-21820
> Project: HBase
> Issue Type: Sub-task
> Reporter: Yi Mei
> Assignee: Yi Mei
> Priority: Major
> Attachments: HBASE-21820.master.001.patch,
> HBASE-21820.master.002.patch, HBASE-21820.master.003.patch,
> HBASE-21820.master.004.patch, HBASE-21820.master.005.patch
>
>
> There are two kinds of quota scope: CLUSTER and MACHINE. CLUSTER quota means
> quota limit is shared by all machines of cluster. MACHINE quota means quota
> limit is used by single region server.
> Currently, all set quota operations use MACHINE scope as default and CLUSTER
> scope has not been implemented. So open this issue to implement CLUSTER quota
> scope.
> To split cluster quota limit to machines, the basic idea is for user,
> namespace, user over namespace quota, use [ClusterLimit / RSNum] as machine
> limit. For table and user over table quota, use [ClusterLimit /
> TotalTableRegionNum * MachineTableRegionNum] as machine limit. Suggestions
> are welcomed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
