hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
Date Wed, 01 Apr 2015 10:48:52 GMT

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

Hadoop QA commented on HBASE-13376:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12708658/HBASE-13376_98.patch
  against master branch at commit 6415742c3757ca72080ca63372d1a0f82ac7607e.
  ATTACHMENT ID: 12708658

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/13519//console

This message is automatically generated.

> 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: HBASE-13376_98.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