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 Thu, 09 Apr 2015 06:36:13 GMT

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

Mikhail Antonov commented on HBASE-13103:


bq. I think I'd prefer to trigger this manually
You mean - you'd prefer to do splits and merges manually, or you'd prefer to kick the "reshaping"
manually (via admin command, rather than letting it run as a chore)?

I'm thinking what could be done to make it safer and more conservative, while still reliving
cluster admin of at least some housekeeping tasks. If this isn't safe, most people probably
just won't turn it on..

 - since as you said, split decisions are generally safer than merge decisions, could have
policy which is much more conservative in merging, than it is in splitting
 - regarding the load..What's there in ServerLoad and RegionLoad won't suffice you think?
Would it help it we grab some OS-level info in ServerLoad (or similar class)?

> [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
>             Fix For: 2.0.0, 1.1.0
>         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

View raw message