Historically, Apache HBase treats all tables, users, and workloads with equal weight. This approach is sufficient for a single workload, but when multiple users and multiple workloads were applied on the same cluster or table, conflicts can arise. Fortunately, starting with HBase in CDH 5.2 (HBase 0.98 + backports), workloads and users can now be prioritized.
One can categorize the approaches to this multi-tenancy problem in three ways:
- Physical isolation or partitioning –
The post New in CDH 5.2: Improvements for Running Multiple Workloads on a Single HBase Cluster appeared first on Cloudera Engineering Blog.