hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9092) OpenRegion could be ignored by mistake
Date Tue, 30 Jul 2013 21:13:48 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724440#comment-13724440

Jimmy Xiang commented on HBASE-9092:

That's the region stuck in transition:

2013-07-30 12:49:30,857 INFO  [RpcServer.handler=2,port=35619] regionserver.HRegionServer(3468):
Receiving OPEN for the region:testOpenFailedUnrecoverable,A,1375188570630.e760841b763bd2e8e453af3b6c7c7b6b.
, which we are already trying to OPEN - ignoring this new request for this region.
> 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
> Looked into failed test:$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.
> 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

View raw message