[
https://issues.apache.org/jira/browse/HBASE-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680826#comment-16680826
]
Hudson commented on HBASE-21439:
--------------------------------
Results for branch branch-2.0
[build #1068 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1068/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1068//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1068//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1068//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> StochasticLoadBalancer RegionLoads aren’t being used in RegionLoad cost
> functions
> ---------------------------------------------------------------------------------
>
> Key: HBASE-21439
> URL: https://issues.apache.org/jira/browse/HBASE-21439
> Project: HBase
> Issue Type: Bug
> Components: Balancer
> Affects Versions: 1.3.2.1, 2.0.2
> Reporter: Ben Lau
> Assignee: Ben Lau
> Priority: Major
> Fix For: 3.0.0, 1.5.0, 1.3.3, 2.2.0, 2.0.3, 1.4.9, 2.1.2
>
> Attachments: HBASE-21439-addendum-master.patch,
> HBASE-21439-branch-1.patch, HBASE-21439-branch-1.patch,
> HBASE-21439-master.patch
>
>
> In StochasticLoadBalancer.updateRegionLoad() the region loads are being put
> into the map with Bytes.toString(regionName).
> First, this is a problem because Bytes.toString() assumes that the byte array
> is a UTF8 encoded String but there is no guarantee that regionName bytes are
> legal UTF8.
> Secondly, in BaseLoadBalancer.registerRegion, we are reading the region loads
> out of the load map not using Bytes.toString() but using
> region.getRegionNameAsString() and region.getEncodedName(). So the load
> balancer will not see or use any of the cluster's RegionLoad history.
> There are 2 primary ways to solve this issue, assuming we want to stay with
> String keys for the load map (seems reasonable to aid debugging). We can
> either fix updateRegionLoad to store the regionName as a string properly or
> we can update both the reader & writer to use a new common valid String
> representation.
> Will post a patch assuming we want to pursue the original intention, i.e.
> store regionNameAsAString for the loadmap key, but I'm open to fixing this a
> different way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
