[
https://issues.apache.org/jira/browse/HBASE-17658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108048#comment-16108048
]
Hudson commented on HBASE-17658:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #228 (See
[https://builds.apache.org/job/HBase-1.3-JDK8/228/])
HBASE-17658 Fix bookkeeping error with max regions for a table (chia7712: rev
c799649a094e62e73be55cbe5889c56a5fa55e1a)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/master/balancer/TestBaseLoadBalancer.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/BaseLoadBalancer.java
> Fix bookkeeping error with max regions for a table
> --------------------------------------------------
>
> Key: HBASE-17658
> URL: https://issues.apache.org/jira/browse/HBASE-17658
> Project: HBase
> Issue Type: Bug
> Components: Balancer
> Reporter: Tim Brown
> Assignee: Tim Brown
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.2.7
>
> Attachments: JIRA-17658.master.001.patch
>
>
> Currently when numMaxRegionsPerTable of a given table increases above the
> current maximum, the value is not properly updated. This means that the cost
> for Table Skew cannot get worse for a given region move during the balancer
> process leading to an imbalanced cluster with respect to Table Skew.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
