[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576402#comment-13576402
]
Francis Liu commented on HBASE-6721:
------------------------------------
{quote}
With this, master, zk and META are still shared across different groups with
little isolation guarantees or SLAs. I am wondering whether this is worth the
effort without having proper multi-tenancy at all levels.
{quote}
The isolation it provides has been very useful for us. We already have this
deployed on 2 clusters. I don't see sharing the master as an issue as
interaction to it is normally administrative. As for ZK, there's an effort to
make it highly scalable if the majority of clients are read-only. Regarding
META, you can have an group which serves only internal tables.
{quote}
I am wondering whether this is worth the effort without having proper
multi-tenancy at all levels. Isn't it way more easier to install multiple
clusters?
{quote}
This is much more easier to operate (installing, reallocating servers, tables,
etc) while providing us the level of isolation we need. Interacting with it is
easier as well, one single configuration file to access any of the tables (if
ACLs permit). Keep in mind this does not preclude adding more multi-tenancy
features (ie rate limiting, priorities, quotas, etc). This is just the first
step, one which we felt provided the biggest gains as well as adding a new
primitive we can build upon.
> RegionServer Group based Assignment
> -----------------------------------
>
> Key: HBASE-6721
> URL: https://issues.apache.org/jira/browse/HBASE-6721
> Project: HBase
> Issue Type: New Feature
> Reporter: Francis Liu
> Assignee: Vandana Ayyalasomayajula
> Fix For: 0.96.0
>
> Attachments: HBASE-6721_94_2.patch, HBASE-6721_94_3.patch,
> HBASE-6721_94_3.patch, HBASE-6721_94_4.patch, HBASE-6721_94_5.patch,
> HBASE-6721_94_6.patch, HBASE-6721_94_7.patch, HBASE-6721_94.patch,
> HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf
>
>
> In multi-tenant deployments of HBase, it is likely that a RegionServer will
> be serving out regions from a number of different tables owned by various
> client applications. Being able to group a subset of running RegionServers
> and assign specific tables to it, provides a client application a level of
> isolation and resource allocation.
> The proposal essentially is to have an AssignmentManager which is aware of
> RegionServer groups and assigns tables to region servers based on groupings.
> Load balancing will occur on a per group basis as well.
> This is essentially a simplification of the approach taken in HBASE-4120. See
> attached document.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
