[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720273#comment-14720273
]
Elliott Clark commented on HBASE-6721:
--------------------------------------
I'm still officially -1 as long as this is built into the core. 99.99%(assuming
10k hbase users) of HBase users should never ever run something like this. It
will make an already very operationally complex system un-workable. Because of
that anything that's in the default code, adds to the default admin, and is
built in is something I can't see ever being ok with.
All of this has already been tried at FB and it was a mistake. This ends up
looking functionally very similar to 0.89-fb's favored nodes. ( Only assign
regions to specific set of machines that's configured by the admin ). It's so
bad that almost every time we try and solve an issue on a cluster with favored
nodes, the first thing we do is turn off the balancer so that we don't have to
worry about which nodes are configured to have with regions. That's literally
step one of debugging. Turn off this feature.
We'll have a party when FB no longer has this operational nightmare. I won't
sign anyone up for the same. I won't sign myself up for the same.
So I'm -1 on anything that I can't completely remove. RM -RF.
* Assignment manager is already too complex adding more complexity is awful
* region movement is already too stateful. Adding more is awful
* configuration of HBase is already way too complex. Multiplying that with
multiple groups is awful.
* Admin already has way too many things for users to do that cause issue.
Adding more ways for a cluster to be borked is awful.
> 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: Francis Liu
> Labels: hbase-6721
> Attachments: 6721-master-webUI.patch, HBASE-6721
> GroupBasedLoadBalancer Sequence Diagram.xml, HBASE-6721-DesigDoc.pdf,
> HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf,
> HBASE-6721_0.98_2.patch, HBASE-6721_10.patch, HBASE-6721_11.patch,
> HBASE-6721_12.patch, HBASE-6721_8.patch, HBASE-6721_9.patch,
> HBASE-6721_9.patch, HBASE-6721_94.patch, HBASE-6721_94.patch,
> 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_98_1.patch, HBASE-6721_98_2.patch,
> HBASE-6721_hbase-6721_addendum.patch, HBASE-6721_trunk.patch,
> HBASE-6721_trunk.patch, HBASE-6721_trunk.patch, HBASE-6721_trunk1.patch,
> HBASE-6721_trunk2.patch, balanceCluster Sequence Diagram.svg,
> immediateAssignments Sequence Diagram.svg, randomAssignment Sequence
> Diagram.svg, retainAssignment Sequence Diagram.svg, roundRobinAssignment
> Sequence Diagram.svg
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
