[
https://issues.apache.org/jira/browse/HBASE-10994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975849#comment-13975849
]
James Taylor commented on HBASE-10994:
--------------------------------------
For existing support of multi-tenancy in Apache Phoenix, see here:
http://phoenix.incubator.apache.org/multi-tenancy.html. I think to do
multi-tenancy in a good way, you need to hide a lot of details behind a good
client API. This is what Apache Phoenix provides.
> 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)
