[
https://issues.apache.org/jira/browse/HBASE-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346377#comment-14346377
]
zhangduo commented on HBASE-13150:
----------------------------------
Seems this is the last enemy.
This is what I have found now. Hope it helps.
{noformat}
2015-03-03 22:17:04,776 INFO
[asf900.gq1.ygridcore.net,35522,1425421016549-org.apache.hadoop.hbase.master.handler.DisableTableHandler$BulkDisabler-4]
master.RegionStateStore(207): Updating row
testRegionTransitionOperations,eee,1425421019650.9d08f4e7ce46a76e88b9e5265b81ff83.
with state=PENDING_CLOSE
2015-03-03 22:17:04,776 INFO [PriorityRpcServer.handler=7,queue=1,port=45988]
regionserver.RSRpcServices(1347): Open
testRegionTransitionOperations,yyy,1425421019650.e2998ed5019dc219cc3c0112541c0cdf.
{noformat}
Grep e2998ed5019dc219cc3c0112541c0cdf, you can see that this should be the last
stage when moving a region. So it means we begin to disable the table when
there are region transitions that have not finished yet.
So this maybe an insufficient waitForRITtoBeZero implementation. But I think
disable table should deal with this situation. It is not acceptable that
disable a table will fail if there are regions in transition I think.
> 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)
