Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 18 Sep 2015 18:26:05 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12606272.1346866872000.14674.1442600765016@Atlassian.JIRA>
In-Reply-To: <JIRA.12606272.1346866872000@Atlassian.JIRA>
References: <JIRA.12606272.1346866872000@Atlassian.JIRA>
 <JIRA.12606272.1346866872857@arcas>
Subject: [jira] [Commented] (HBASE-6721) RegionServer Group based Assignment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-6721?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1487=
6096#comment-14876096 ]=20

Andrew Purtell commented on HBASE-6721:
---------------------------------------

bq. Andrew Purtell The new patch is based off of current master. Should we =
just replace the current branch with a new branch to go with the new patch?

I would say so if you want it.=20

bq. Also was wondering since this is now cp-based. Do we still need a branc=
h?

Up to you. We can rebase or delete, either way let me know. =20

Some issues with the current security integration. Coprocessors can't call =
into the internals of other coprocessors. I understand why this was done, b=
ut we can't have it. Coprocessors calling into the internals of other copro=
cessors, this is a non-negotiable point for the sake of sanity in maintenan=
ce of separate optional extensions. It's a catch-22 imposed on this change =
by the requirement it be a coprocessor only implementation.

What I would suggest is introduce into the MasterObserver API hooks for the=
 group admin APIs. Let the implementation of the group admin APIs and the a=
uthoritative security decisions both be separate mix-ins provided by differ=
ent coprocessors. There needs to be common plumbing for the two. That belon=
gs in MasterObserver. The plumbing could look like:
- MasterObserver support for pre/post group admin API action hooks
- In GroupAdminEndpoint, get the coprocessor host with getMasterCoprocessor=
Host()
- Invoke the public (technically, LimitedPrivate(COPROC)) APIs for pre/post=
 group admin API actions.

This is much more in spirit with current interfaces and audience scoping. I=
t also addresses concerns about zero impact in the default case. Those upca=
lls will never be made unless the GroupAdminEndpoint is installed.

> 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 GroupBasedLoadBa=
lancer Sequence Diagram.xml, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.p=
df, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, HBASE-6721_0.98_2.pat=
ch, HBASE-6721_10.patch, HBASE-6721_11.patch, HBASE-6721_12.patch, HBASE-67=
21_13.patch, HBASE-6721_14.patch, HBASE-6721_8.patch, HBASE-6721_9.patch, H=
BASE-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.patc=
h, HBASE-6721_94_5.patch, HBASE-6721_94_6.patch, HBASE-6721_94_7.patch, HBA=
SE-6721_98_1.patch, HBASE-6721_98_2.patch, HBASE-6721_hbase-6721_addendum.p=
atch, HBASE-6721_trunk.patch, HBASE-6721_trunk.patch, HBASE-6721_trunk.patc=
h, HBASE-6721_trunk1.patch, HBASE-6721_trunk2.patch, balanceCluster Sequenc=
e Diagram.svg, immediateAssignments Sequence Diagram.svg, randomAssignment =
Sequence Diagram.svg, retainAssignment Sequence Diagram.svg, roundRobinAssi=
gnment Sequence Diagram.svg
>
>
> In multi-tenant deployments of HBase, it is likely that a RegionServer wi=
ll be serving out regions from a number of different tables owned by variou=
s client applications. Being able to group a subset of running RegionServer=
s and assign specific tables to it, provides a client application a level o=
f isolation and resource allocation.
> The proposal essentially is to have an AssignmentManager which is aware o=
f RegionServer groups and assigns tables to region servers based on groupin=
gs. Load balancing will occur on a per group basis as well.=20
> 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)