hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adela Maznikar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10109) [0.89-fb] Balance #regions/RS better when creating new table
Date Tue, 10 Dec 2013 21:50:08 GMT

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

Adela Maznikar commented on HBASE-10109:
----------------------------------------

The current approach assigns the regions in round robin fashion, but taking the racks into
consideration (for each rack, for each regionserver , we assign a region). And we always start
with the same rack. Additional improvement is to merge all regionservers together and then
do the round robin assignment which would give us balance per regionserver. 

> [0.89-fb] Balance #regions/RS better when creating new table
> ------------------------------------------------------------
>
>                 Key: HBASE-10109
>                 URL: https://issues.apache.org/jira/browse/HBASE-10109
>             Project: HBase
>          Issue Type: Improvement
>          Components: Region Assignment
>    Affects Versions: 0.89-fb
>            Reporter: Adela Maznikar
>            Assignee: Adela Maznikar
>            Priority: Minor
>             Fix For: 0.89-fb
>
>
> When a new table is created we place the primary locations for the regions in a round
robin fashion. Because we do this for every newly created table it is possible that some regionservers
end up with more regions than the others and if there are more tables in the cluster the difference
between a min and max #regions per RS can be larger. 
> One small optimization is to sort the RS in ascending order before assigning them regions.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message