hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13103) [ergonomics] add region size balancing as a feature of master
Date Wed, 20 Jan 2016 08:46:40 GMT

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

Mikhail Antonov commented on HBASE-13103:

[~stack] - missed that comments, sorry. I've assigned to myself jira to create refguide on

Normalization is operated on/off in the same way as balancer or other znode-based trackers.
I'm actually torn on whether we should have it on or off by default. Having it on by default
sounds a bit aggressive, having it off might delay adoption. What do you think? I'm inclined
to have it on by default with appropriate release note. If it misbehaves for someone, it's
one shell command to disable completely, and any feedback on such case would help to improve
"self-healing" heuristics.

> [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: Improvement
>          Components: Balancer, Usability
>            Reporter: Nick Dimiduk
>            Assignee: Mikhail Antonov
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>         Attachments: HBASE-13103-branch-1.v3.patch, HBASE-13103-v0.patch, HBASE-13103-v1.patch,
HBASE-13103-v2.patch, HBASE-13103-v3.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

View raw message