[ https://issues.apache.org/jira/browse/HBASE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
He Liangliang updated HBASE-9817: --------------------------------- Attachment: HBASE-9817.patch > Add throughput quota and enforce hard limits > -------------------------------------------- > > Key: HBASE-9817 > URL: https://issues.apache.org/jira/browse/HBASE-9817 > Project: HBase > Issue Type: New Feature > Components: Coprocessors > Reporter: He Liangliang > Assignee: He Liangliang > Attachments: HBASE-9817.patch > > > There is planning to add region count and table count quota mentioned in > HBASE-8410. However, it's also quite useful to control the requesting > throughput inside the region server. For example, we don't want a data > dumping task affecting the online services and it's better to enforce the > throughput quota inside HBase. Another common scenario is multi-tenancy, i.e. > a cluster is shared by multiple applications. > The following rules will be supported: > 1. per user quota > limits the total read/write throughput initiated by a single user on any > table. > 2. per (user, table) quota > limits the total read/write throughput initiated by a single user on a > specified table. > The implementation will use coprocessor to intercept and check each request > on each region. And each region server allocate a portion of quota from the > total specified quota (for that user or user + table) based on the portion of > active regions (the whole cluster or the specified table) assigned on that > region server. The request will be rejected or delayed if the limit is > reached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)