You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2011/04/14 19:39:06 UTC

[jira] [Commented] (HBASE-3779) Allow split regions to be placed on different region servers

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

Jean-Daniel Cryans commented on HBASE-3779:
-------------------------------------------

This shouldn't be done inline with the split tho as it will take that whole key space offline for even longer. The way it's currently is actually an optimization in that regard.

What could be done tho is moving the region with the less load after the dust settles but even then, you might want a different behavior for the heavy import scenario and the realtime serving one. In the former, if the import is even across the regions, the region servers should all be splitting as much as the others so moving regions does no good.

> Allow split regions to be placed on different region servers
> ------------------------------------------------------------
>
>                 Key: HBASE-3779
>                 URL: https://issues.apache.org/jira/browse/HBASE-3779
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.90.2
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>
> Currently daughter regions are placed on the same region server where the parent region was.
> Stanislav Barton mentioned the idea that load information should be considered when placing the daughter regions.
> The rationale is that the daughter regions tend to receive more writes. So it would be beneficial to place at least one daughter region on a different region server.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira