hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3779) Allow split regions to be placed on different region servers
Date Tue, 19 Apr 2011 16:54:05 GMT

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

Ted Yu commented on HBASE-3779:
-------------------------------

The improvement from HBASE-3609 doesn't cover this JIRA in the following scenario:
Region server A isn't overloaded in terms of number of regions on it. One of the regions of
table B is actively written to and is split. Still, there is no guarantee that number of regions
on A is above the sloppiness introduced by HBASE-3681.

The introduction of new parameter is mostly due to different opinions on how the daughters
should be handled.

> 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
>         Attachments: 3779.patch
>
>
> 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

Mime
View raw message