[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700035#comment-14700035
]
Andrew Purtell commented on HBASE-6721:
---------------------------------------
{quote}
bq. The tool says hbase-6721-0.98 is 100% binary compatible with 0.98.13, with
some source level incompatibility of mild concern in the MasterObserver
interface.
This is prolly because of the new methods this patch adds to the interface.
This shouldn't be a concern then?
{quote}
Yes, it will be a concern for things like Apache Phoenix. (See their
IndexMasterObserver, etc.) We can handle this by using compatibility helpers
that won't attempt to invoke the new APIs on MasterObservers that do not
implement them. We do something like this in WALCoprocessorHost.
> 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_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_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)
