[
https://issues.apache.org/jira/browse/HBASE-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348352#comment-14348352
]
Andrey Stepachev commented on HBASE-13150:
------------------------------------------
[~zhangduo] at first I tried to make thread BulkUnassign more intelligent, it
peeks regions and later rechecks that all regions not OPENED, if so it
rescheduled. But later I found piece of code removed in HBASE-13076 in this
test never failed in my setup (2/3 times it failed before) flackery
> TestMasterObserver failing disable table at end of test
> -------------------------------------------------------
>
> Key: HBASE-13150
> URL: https://issues.apache.org/jira/browse/HBASE-13150
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
>
> I see in
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-TRUNK/6202/testReport/junit/org.apache.hadoop.hbase.coprocessor/TestMasterObserver/testRegionTransitionOperations/
> , now we have added in timeouts, that we are failing to disable a table. It
> looks like table is disabled but regions are being opened on the disabled
> table still, like HBASE-6537
> Let me see if can figure why this happening. Will be back.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)