[HBASE-10994] HBase Multi-Tenancy

• Type: Umbrella
• Status: Closed
• Priority: Minor
• Resolution: Implemented
• Labels: Phoenix multitenancy quota
• Assignee: Unassigned
• Reporter: Matteo Bertozzi
• Created: 16/Apr/14 02:21
• Updated: 17/Jun/22 05:33
• Resolved: 11/Jun/22 18:13

Description

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

Issue Links

• incorporates: HBASE-11598 Add simple rpc throttling
• is related to: HBASE-13098 HBase Connection Control
• is related to: HBASE-11355 a couple of callQueue related improvements
• relates to: HBASE-8410 Basic quota support for namespaces
• relates to: HBASE-11724 Add to RWQueueRpcExecutor the ability to split get and scan handlers

Sub-Tasks

• Deprioritize long-running scanners: Closed
• Add simple rpc throttling: Closed
• table creations quota: Closed
• Document HBase Quota: Closed