hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13103) [ergonomics] add region size balancing as a feature of master
Date Tue, 07 Apr 2015 17:24:13 GMT

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

Nick Dimiduk commented on HBASE-13103:
--------------------------------------

Nice work [~mantonov]. I left some comments over on RB.

bq. being able to choose which table to normalize

I'd like this to eventually be a globally enabled feature, with opt-out via table configuration.
For it's initial commit, it should probably be opt-in instead. Having a global kill switch
is probably a good idea too.

bq. need to define normalization rules more strictly (including priority of operations? if
table has both types of outlier in the ranks of its regions - too small and too big regions,
then what action is more urgent)

Yes, priorities will become a useful feature. I think what you have here is a nice, committable
first pass though.

bq. run normalization across several tables in parallel - is that something we should/shouldn't
do

Probably that's something we can and should do. Can be future patch though.

bq. detecting currently running merges and splits. Current simple rules are just that we don't
touch system tables and tables with less than 3 regions.

Why no touch regions with fewer than 3 regions?

These are all good questions for our operator friends. [~eclark], [~toffer], [~lhofhansl]
any opinions here? Think you fellas may be interested in this feature.

> [ergonomics] add region size balancing as a feature of master
> -------------------------------------------------------------
>
>                 Key: HBASE-13103
>                 URL: https://issues.apache.org/jira/browse/HBASE-13103
>             Project: HBase
>          Issue Type: Brainstorming
>          Components: Usability
>            Reporter: Nick Dimiduk
>            Assignee: Mikhail Antonov
>         Attachments: HBASE-13103-v0.patch
>
>
> Often enough, folks miss-judge split points or otherwise end up with a suboptimal number
of regions. We should have an automated, reliable way to "reshape" or "balance" a table's
region boundaries. This would be for tables that contain existing data. This might look like:
> {noformat}
> Admin#reshapeTable(TableName, int numSplits);
> {noformat}
> or from the shell:
> {noformat}
> > reshape TABLE, numSplits
> {noformat}
> Better still would be to have a maintenance process, similar to the existing Balancer
that runs AssignmentManager on an interval, to run the above "reshape" operation on an interval.
That way, the cluster will automatically self-correct toward a desirable state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message