[
https://issues.apache.org/jira/browse/HBASE-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368222#comment-14368222
]
Esteban Gutierrez commented on HBASE-13114:
-------------------------------------------
Dug into this today, the problem is very similar to HBASE-13182, which is
basically that Admin is not really synchronous and it can return earlier when
getTableDescriptorByTableName() is null. If we add a sleep of few 100 ms before
scanning META after deleting the table the problem is less frequent, however
that is only masquerading the real problem. The best option seems to use a
latch for now in the same way [~mbertozzi] did in HBASE-13179 and HBASE-13182.
> [UNITTEST] TestEnableTableHandler.testDeleteForSureClearsAllTableRowsFromMeta
> -----------------------------------------------------------------------------
>
> Key: HBASE-13114
> URL: https://issues.apache.org/jira/browse/HBASE-13114
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
> Attachments: 13114.txt
>
>
> I've seen this fail a few times. It just happened now on internal rig.
> Looking into it....
> {code}
> REGRESSION:
> org.apache.hadoop.hbase.master.handler.TestEnableTableHandler.testDeleteForSureClearsAllTableRowsFromMeta
> Error Message:
> expected:<0> but was:<1>
> Stack Trace:
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.hbase.master.handler.TestEnableTableHandler.testDeleteForSureClearsAllTableRowsFromMeta(TestEnableTableHandler.java:151)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
