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] [Updated] (HBASE-7981) TestSplitTransactionOnCluster.testShutdownFixupWhenDaughterHasSplit failed in 0.95 build #11
Date Thu, 07 Mar 2013 02:54:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-7981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ramkrishna.s.vasudevan updated HBASE-7981:
------------------------------------------

    Attachment: HBASE-7981_1.patch

The timeout was increased for debugging purpose. I have removed that.
The idea here is when the region is tried to move away from the RS that holds the META, the
region is actually closed. So the isClosed returns true.
The new check that is added to see if region is splittable internally checks for isClosed.
 But we are doing it on the older list of regions.  We need to refresh the regions list. 
The failure will happen only when there is a movement of region takes places from RS having
META to another RS.
                
> TestSplitTransactionOnCluster.testShutdownFixupWhenDaughterHasSplit failed in 0.95 build
#11
> --------------------------------------------------------------------------------------------
>
>                 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

Mime
View raw message