hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vandana Ayyalasomayajula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
Date Tue, 11 Aug 2015 17:25:46 GMT

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

Vandana Ayyalasomayajula commented on HBASE-13376:
--------------------------------------------------

On my machine, the test passes, 

{quote}
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2
Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 755.196 sec - in org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2

{quote} 

Let me quickly check from the previous builds, the running time of this test.



> Improvements to Stochastic load balancer
> ----------------------------------------
>
>                 Key: HBASE-13376
>                 URL: https://issues.apache.org/jira/browse/HBASE-13376
>             Project: HBase
>          Issue Type: Improvement
>          Components: Balancer
>    Affects Versions: 1.0.0, 0.98.12
>            Reporter: Vandana Ayyalasomayajula
>            Assignee: Vandana Ayyalasomayajula
>            Priority: Minor
>         Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt,
HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch,
HBASE-13376_3.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch
>
>
> There are two things this jira tries to address:
> 1. The locality picker in the stochastic balancer does not pick regions with least locality
as candidates for swap/move. So when any user configures locality cost in the configs, the
balancer does not always seems to move regions with bad locality. 
> 2. When a cluster has equal number of loaded regions, it always picks the first one.
It should pick a random region on one of the equally loaded servers. This improves a chance
of finding a good candidate, when load picker is invoked several times. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message