[
https://issues.apache.org/jira/browse/HBASE-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-7686:
-----------------------------------
Attachment: HBASE-7686-v0.patch
I've looked a bit into this since is showing up in my jenkins.
There're a couple of strange things like the MockedSplitTransaction() with a
null splitRow and no call to prepare()
but trying to look into the failures seems that most of them are caused by
regions not available...
v0 patch, tries to look for a splittable region (isAvailable() &&
!hasReferences()) and adds the missing splitRow/prepare() just to be correct
even if they are not really needed since the SplitTransaction is mocked.
> TestSplitTransactionOnCluster fails occasionally in trunk builds
> ----------------------------------------------------------------
>
> Key: HBASE-7686
> URL: https://issues.apache.org/jira/browse/HBASE-7686
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Priority: Critical
> Fix For: 0.95.0
>
> Attachments: HBASE-7686-v0.patch
>
>
> From trunk build #3808:
> {code}
> testShouldFailSplitIfZNodeDoesNotExistDueToPrevRollBack(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
> test timed out after 20000 milliseconds
>
> testMasterRestartWhenSplittingIsPartial(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
> test timed out after 300000 milliseconds
>
> testExistingZnodeBlocksSplitAndWeRollback(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
> test timed out after 300000 milliseconds
> {code}
> From HBase-TRUNK-on-Hadoop-2.0.0 #378 :
> {code}
> testShutdownSimpleFixup(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
> Region not moved off .META. server
>
> testShouldFailSplitIfZNodeDoesNotExistDueToPrevRollBack(org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster):
> test timed out after 20000 milliseconds
> {code}
--
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
