[
https://issues.apache.org/jira/browse/HBASE-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346952#comment-14346952
]
zhangduo commented on HBASE-13150:
----------------------------------
{noformat}
2015-03-03 22:17:04,715 DEBUG [Thread-268] master.AssignmentManager(1295):
Starting unassign of
testRegionTransitionOperations,yyy,1425421019650.e2998ed5019dc219cc3c0112541c0cdf.
(offlining), current state: {e2998ed5019dc219cc3c0112541c0cdf state=OPEN,
ts=1425421021849, server=asf900.gq1.ygridcore.net,44226,1425421017118}
2015-03-03 22:17:04,758 INFO [MASTER_TABLE_OPERATIONS-asf900:35522-0]
handler.DisableTableHandler(123): Attempting to disable table
testRegionTransitionOperations
2015-03-03 22:17:04,765 INFO [MASTER_TABLE_OPERATIONS-asf900:35522-0]
handler.DisableTableHandler(166): Offlining 26 regions.
{noformat}
There is only one log line for unassigning e2998ed5019dc219cc3c0112541c0cdf and
it is before we disabling testRegionTransitionOperations so it should be the
region moving(offline and then online). The number of regions in log is
right(26 regions), but seems we skip the offline process if region is in
transition.
{code:title=DisableTableHandler.java}
@Override
protected void populatePool(ExecutorService pool) {
RegionStates regionStates = assignmentManager.getRegionStates();
for (HRegionInfo region: regions) {
if (regionStates.isRegionInTransition(region)
&& !regionStates.isRegionInState(region,
RegionState.State.FAILED_CLOSE)) {
continue;
}
final HRegionInfo hri = region;
pool.execute(Trace.wrap("DisableTableHandler.BulkDisabler",new
Runnable() {
public void run() {
assignmentManager.unassign(hri);
}
}));
}
}
{code}
So the problem maybe the code how we deal with the regions in transition state
when disabling a table? I have not found the code yet.
> 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)
