hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7981) TestSplitTransactionOnCluster.testShutdownFixupWhenDaughterHasSplit failed in 0.95 build #11
Date Thu, 07 Mar 2013 03:42:12 GMT

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

ramkrishna.s.vasudevan commented on HBASE-7981:

Actually the patch that i attached is for the testcase testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback.

https://builds.apache.org/job/hbase-0.95/32/testReport/ shows the error that i pointed out.
bq.Isn't ensureTableRegionNotOnSameServerAsMeta() will take care that the region which we
will split is not co-hosted with a meta region.

That causes this problem.  The regions list is collected even before this ensureTableRegionNotOnSameServerAsMeta()
is called.  So when we try to work on that region object the isClosed becomes true.

> TestSplitTransactionOnCluster.testShutdownFixupWhenDaughterHasSplit failed in 0.95 build
> --------------------------------------------------------------------------------------------
>                 Key: HBASE-7981
>                 URL: https://issues.apache.org/jira/browse/HBASE-7981
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.95.0
>         Attachments: 7981.extra.logging.txt, 7981.extra.logging.txt, 7981v2.extra.logging.txt,
HBASE-7981_1.patch, HBASE-7981.patch
> https://builds.apache.org/job/hbase-0.95/11/testReport/junit/org.apache.hadoop.hbase.regionserver/TestSplitTransactionOnCluster/testShutdownFixupWhenDaughterHasSplit/
> Hard to tell which region is missing post crash.  Not logged.

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