[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720921#comment-14720921
]
Andrew Purtell commented on HBASE-6721:
---------------------------------------
Let's not let the perfect be the enemy of the good. A "proper" multi-layer
admission control change isn't on the table, it isn't on anyone's roadmap, it
isn't even something proposed on a JIRA and/or in a design document. Even if we
have a proposal for HBase this will certainly be considered imperfect and
incomplete by some without 100% agreement and a plan at the HDFS level, and
getting that is as likely as finding a unicorn wandering around downtown SF.
(Ok... maybe a horse dressed to look like a unicorn could be a thing...)
Meanwhile we have a patch on deck and we need to be evaluating it and its
contributor's concerns on their merit.
This is something that one of our esteemed users runs in production, is
persistent about getting in and responsive to feedback, and both of those
things in my opinion should carry a lot of weight. The same kind of weight that
previously proposed changes like HFileV2 or the 0.90 master rewrite (remember
that?), or the memcache-based block cache carried, or pending IPv6 related
changes.
That said, I don't think it's ready to be merged into master. We have it up in
a feature branch. Let's continue that, address concerns, make sure it's totally
optional for those who don't want it, measure its impact.
> 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)
