[
https://issues.apache.org/jira/browse/HBASE-9092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727177#comment-13727177
]
Hudson commented on HBASE-9092:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #647 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/647/])
HBASE-9092 OpenRegion could be ignored by mistake (jxiang: rev 1509384)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManagerOnCluster.java
> 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
