[
https://issues.apache.org/jira/browse/HBASE-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346959#comment-14346959
]
Andrey Stepachev commented on HBASE-13150:
------------------------------------------
That is the same situation here, I think.
https://issues.apache.org/jira/browse/HBASE-13076
bq. Table become ENABLED, thats leads to regions instructed to assign
immediately on onRegionClosed. BulkDisabler will not know about that and will
wait indefinitely, because it will not issue unassign for newly opened regions.
> 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)
