Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 14 Jun 2015 09:58:01 +0000 (UTC)
From: "Mikhail Antonov (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12777641.1424891950000.66731.1434275881701@Atlassian.JIRA>
In-Reply-To: <JIRA.12777641.1424891950000@Atlassian.JIRA>
References: <JIRA.12777641.1424891950000@Atlassian.JIRA>
 <JIRA.12777641.1424891950333@arcas>
Subject: [jira] [Commented] (HBASE-13103) [ergonomics] add region size
 balancing as a feature of master
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mikhail Antonov commented on HBASE-13103:
-----------------------------------------

bq. it'll be good to get this out for folks to start playing with it in 1.1.0.
That's what I'm thinking too. Apparently nobody is going to turn it on in production env (yet); thinking what would be the most conservative yet usable strategy folks may want to play with in some sandbox clusters?

> [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
>
>         Attachments: HBASE-13103-v0.patch, HBASE-13103-v1.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)