You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Matteo Bertozzi (JIRA)" <ji...@apache.org> on 2014/04/16 04:22:18 UTC

[jira] [Created] (HBASE-10994) HBase Multi-Tenancy

Matteo Bertozzi created HBASE-10994:
---------------------------------------

             Summary: 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


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)