[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720602#comment-14720602
]
Enis Soztutar commented on HBASE-6721:
--------------------------------------
bq. This patch breaks ipv6.
bq. This patch has Copy Paste code.
bq. This patch doesn't have the correct headers.
bq. This patch doesn't load meta's hri from disk on move.
These are review comments that are not related to the discussion right now.
bq. If we want multi-tenancy, then lets do that right. We shouldn't accept
hacks that don't help most users and make getting to the correct solution
harder.
I don't understand your reasoning. Yahoo has been running with this for >1
year, and we have other users that will run with RS groups once it is in. The
way I see it is not a hack, but a step towards better guarantees. Multi-tenancy
and isolation will never be perfect and will always be an ongoing effort to
improve it. For example, without making the coprocessors run in a colocated
container, we cannot isolate one tenants co-processors from the others today.
Saying that we should fix EVERY multitenancy/isolation problem which can take
years is not realistic.
bq. Agreed the ops impact should be totally optional.
+1 to this. I think with the patch it is already the case. If you are not using
the feature, you should not be affected in any way. Yes, with RS groups, if you
do not know what you are doing, it is more states and more things can go wrong,
but we are not making it default or anything. Memcache based block cache is
only used by FB and it is just added complexity for remaining users, but we
have it regardless.
> 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)
