You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/08/01 20:33:50 UTC
[jira] [Commented] (HBASE-9092) OpenRegion could be ignored by
mistake
[ https://issues.apache.org/jira/browse/HBASE-9092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726716#comment-13726716 ]
stack commented on HBASE-9092:
------------------------------
+1
I like the call to unassign if FAILED_OPEN before moving on.
> OpenRegion could be ignored by mistake
> --------------------------------------
>
> Key: HBASE-9092
> URL: https://issues.apache.org/jira/browse/HBASE-9092
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9092.patch
>
>
> Looked into failed test: http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/
> In this test run, several tests in TestAssignmentManagerOnCluster failed. Most of them timed out because the first failure testOpenFailedUnrecoverable used too much resource in deleting the table.
> http://54.241.6.143/job/HBase-0.95/org.apache.hbase$hbase-server/721/testReport/org.apache.hadoop.hbase.master/TestAssignmentManagerOnCluster/testOpenFailedUnrecoverable/
> The reason testOpenFailedUnrecoverable failed is that the second openRegion call was ignored since the previous open call was still going on and stayed in OpenRegionHandler#doCleanUpOnFailedOpen for too long (perhaps thread scheduling issue). The second openRegion call was skipped since the region was still in the middle of opening. However, the failed_open event was already processed by master. Therefore the region stuck in transition and the delete table went no where. It is a similar issue as we ran into before while for that time, the region was closing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira