[
https://issues.apache.org/jira/browse/HBASE-13590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518530#comment-14518530
]
Nick Dimiduk commented on HBASE-13590:
--------------------------------------
The three above all terminate after timeout with the following stack
{noformat}
junit.framework.AssertionFailedError: Waiting timed out after [60,000] msec
table enabled in zk,
at junit.framework.Assert.fail(Assert.java:57)
at org.apache.hadoop.hbase.Waiter.waitFor(Waiter.java:209)
at org.apache.hadoop.hbase.Waiter.waitFor(Waiter.java:161)
at
org.apache.hadoop.hbase.HBaseTestingUtility.waitFor(HBaseTestingUtility.java:3772)
at
org.apache.hadoop.hbase.HBaseTestingUtility.waitUntilAllRegionsAssigned(HBaseTestingUtility.java:3226)
at
org.apache.hadoop.hbase.HBaseTestingUtility.waitUntilAllRegionsAssigned(HBaseTestingUtility.java:3177)
at
org.apache.hadoop.hbase.master.handler.TestEnableTableHandler.testEnableTableWithNoRegionServers(TestEnableTableHandler.java:107)
{noformat}
Log shows region either fails to be assigned or fails to online.
> TestEnableTableHandler.testEnableTableWithNoRegionServers is flakey
> -------------------------------------------------------------------
>
> Key: HBASE-13590
> URL: https://issues.apache.org/jira/browse/HBASE-13590
> Project: HBase
> Issue Type: Test
> Components: master
> Reporter: Nick Dimiduk
> Priority: Critical
> Fix For: 2.0.0, 1.1.0, 1.2.0
>
>
> Looking at our [build
> history|https://builds.apache.org/job/HBase-1.1/buildTimeTrend], it seems
> this test is flakey. See builds 429, 431, 439.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
