[
https://issues.apache.org/jira/browse/HBASE-17658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871993#comment-15871993
]
Ted Yu commented on HBASE-17658:
--------------------------------
{code}
testMobGetAtomicity[1](org.apache.hadoop.hbase.TestAcidGuarantees) Time
elapsed: 21.968 sec <<< ERROR!
java.lang.RuntimeException: Deferred
at
org.apache.hadoop.hbase.MultithreadedTestUtil$TestContext.checkException(MultithreadedTestUtil.java:79)
at
org.apache.hadoop.hbase.MultithreadedTestUtil$TestContext.waitFor(MultithreadedTestUtil.java:72)
at
org.apache.hadoop.hbase.TestAcidGuarantees.runTestAtomicity(TestAcidGuarantees.java:388)
at
org.apache.hadoop.hbase.TestAcidGuarantees.testMobGetAtomicity(TestAcidGuarantees.java:435)
{code}
Not related to patch.
> Bookkeeping issue in BaseLoadBalancer for Table Skew
> ----------------------------------------------------
>
> 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
> 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.3.15#6346)