hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10075) add a locality-aware balancer
Date Thu, 05 Dec 2013 14:52:36 GMT

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

Andrew Purtell commented on HBASE-10075:
----------------------------------------

Consider attaching a patch against HBase trunk, the balancer related code has changed significantly
since 0.94 and we bring in new features through trunk first.

> add a locality-aware balancer
> -----------------------------
>
>                 Key: HBASE-10075
>                 URL: https://issues.apache.org/jira/browse/HBASE-10075
>             Project: HBase
>          Issue Type: New Feature
>          Components: Balancer
>    Affects Versions: 0.94.12
>            Reporter: Chengxiang Li
>         Attachments: HBASE-10075.patch
>
>
> basic idea: 
> during rebalance. For each region server, iterate regions, give each region a balance
score, remove the lowest one until the region number of region server reach avg floor. 
> during assignment. match to-be-assigned regions with each active region server as pairs,
give each pair a balance score, the highest win this region. 
> here is the mark formula: 
> (1 – tableRegionNumberOnServer/allTableRegionNumber) * tableBalancerWeight 
> + (1 – regionNumberOnServer/allRegionNumber) * serverBalancerWeight + regionBlockSizeOnServer/regionBlockSize
* localityWeight 
> + (previousServer?1:0) * stickinessWeight 
> there are 4 factors which would influence the final balance score: 
> 1. region balance 
> 2. table region balance 
> 3. region locality 
> 4. region stickiness 
> through adjust the weight of these 4 factors, we can balance the cluster in different
strategy.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message