[
https://issues.apache.org/jira/browse/HBASE-10994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970397#comment-13970397
]
Andrew Purtell commented on HBASE-10994:
----------------------------------------
On namespaces, the document says:
{quote}
Namespaces: Will not be mentioned much in this document, since we are
considering the smallest unity of scalability to make the examples, and
namespaces are just a group of tables, so everytime you see “Table” you can
replace it with “Namespace”. A rule applied to a namespace will be applied to
all the tables in it.
{quote}
Elsewhere, on quotas:
{quote}
>From an implementation point of view quotas will be part of scheduling, since
>we have to block/limit/throttle incoming requests based on the usage. The
>simplest way to implement quotas is by using a “token bucket” algorithm (but
>we will have an interface to make it pluggable).
{quote}
What happens if there is a quota on a namespace, and quotas on tables within?
> HBase Multi-Tenancy
> -------------------
>
> Key: HBASE-10994
> URL: https://issues.apache.org/jira/browse/HBASE-10994
> Project: HBase
> Issue Type: Umbrella
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: multitenancy, quota
>
> Currently HBase treats all tables, users, and workloads in the same way.
> This is ok, until multiple users and workloads are applied on the same
> cluster/table. Some workloads/users must be prioritized over others, and some
> other workloads must not impact others.
> We can separate the problem into three components.
> * Isolation/Partitioning (Physically split on different machines)
> * Scheduling (Prioritize small/interactive workloads vs long/batch workloads)
> * Quotas (Limit a user/table requests/sec or size)
> This is the umbrella jira tracking the multi-tenancy related tasks.
> An initial design document is up for comments here:
> https://docs.google.com/document/d/1ygIwZpDWQuMPdfcryckic6ODi5DHQkrzXKjmOJodfs0
--
This message was sent by Atlassian JIRA
(v6.2#6252)
