[
https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702824#comment-14702824
]
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/12751221/HBASE-13376_v4_0.98.patch
against 0.98 branch at commit 1bb9e3ae966853db8c4138b4abbe14636d7592db.
ATTACHMENT ID: 12751221
{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:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
22 warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
3882 checkstyle errors (more than the master's current 3876 errors).
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15163//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15163//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15163//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15163//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15163//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
> Fix For: 2.0.0, 1.3.0
>
> Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch,
> HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.98_v2.patch,
> 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_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch,
> HBASE-13376_6_branch-1.patch, HBASE-13376_98.patch,
> HBASE-13376_branch-1.patch, HBASE-13376_v3_0.98.patch,
> HBASE-13376_v4_0.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)