hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6721) RegionServer Group based Assignment
Date Tue, 08 Mar 2016 18:40:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185457#comment-15185457
] 

Sean Busbey commented on HBASE-6721:
------------------------------------

bq. Thanks for taking a look at this Sean Busbey. Sorry I meant "root", I mentioned component
because the directory is called "component" which I realize now just makes things confusing.
If this is a bug that'd be in Yetus?

Ah. the directory is named component because of how I set up the jenkins job. That's just
to distinguish it from "test_framework" in a way that I can copy/paste as I set up other projects.

We're definitely running individual modules even after we've determined we have to run at
the top level of the project. That's *probably* a bug in yetus, but I haven't confirmed yet
that we don't do module reordering in [our test personality|https://github.com/apache/hbase/blob/master/dev-support/hbase-personality.sh].
If we do, then the bug could be in our personality rather than yetus proper.

> 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_13.patch,
HBASE-6721_14.patch, HBASE-6721_15.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, hbase-6721-v15-branch-1.1.patch, hbase-6721-v16.patch,
hbase-6721-v17.patch, hbase-6721-v18.patch, hbase-6721-v19.patch, hbase-6721-v20.patch, hbase-6721-v21.patch,
hbase-6721-v22.patch, hbase-6721-v23.patch, hbase-6721-v25.patch, hbase-6721-v26.patch, hbase-6721-v26_draft1.patch,
hbase-6721-v27.patch, hbase-6721-v27.patch, hbase-6721-v27.patch.txt, hbase-6721-v28.patch,
hbase-6721-v28.patch, hbase-6721-v29.patch, 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)

Mime
View raw message