[
https://issues.apache.org/jira/browse/HBASE-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348111#comment-14348111
]
zhangduo commented on HBASE-13150:
----------------------------------
Oh sorry, I found the code.
{code:title=AssignmentManager.java}
private String onRegionOpen(final RegionState current, final HRegionInfo hri,
final ServerName serverName, final RegionStateTransition transition) {
...
if (getTableStateManager().isTableState(hri.getTable(),
TableState.State.DISABLED, TableState.State.DISABLING)) {
invokeUnAssign(hri);
}
...
}
{code}
So let me see if there is a race condition.
> 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)
