hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15277) TestRegionMergeTransactionOnCluster.testWholesomeMerge fails with no connection to master
Date Wed, 24 Feb 2016 06:40:18 GMT

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

stack commented on HBASE-15277:
-------------------------------

All attempts at fixing this test

> TestRegionMergeTransactionOnCluster.testWholesomeMerge fails with no connection to master
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-15277
>                 URL: https://issues.apache.org/jira/browse/HBASE-15277
>             Project: HBase
>          Issue Type: Sub-task
>          Components: test
>            Reporter: stack
>             Fix For: 2.0.0
>
>         Attachments: 15277.patch
>
>
> {code}
> java.io.IOException: connection is closed
> 	at org.apache.hadoop.hbase.MetaTableAccessor.getMetaHTable(MetaTableAccessor.java:254)
> 	at org.apache.hadoop.hbase.MetaTableAccessor.scanMeta(MetaTableAccessor.java:773)
> 	at org.apache.hadoop.hbase.MetaTableAccessor.scanMeta(MetaTableAccessor.java:702)
> 	at org.apache.hadoop.hbase.MetaTableAccessor.getTableRegionsAndLocations(MetaTableAccessor.java:624)
> 	at org.apache.hadoop.hbase.MetaTableAccessor.getTableRegionsAndLocations(MetaTableAccessor.java:575)
> 	at org.apache.hadoop.hbase.regionserver.TestRegionMergeTransactionOnCluster.waitAndVerifyRegionNum(TestRegionMergeTransactionOnCluster.java:426)
> 	at org.apache.hadoop.hbase.regionserver.TestRegionMergeTransactionOnCluster.mergeRegionsAndVerifyRegionNum(TestRegionMergeTransactionOnCluster.java:402)
> 	at org.apache.hadoop.hbase.regionserver.TestRegionMergeTransactionOnCluster.testWholesomeMerge(TestRegionMergeTransactionOnCluster.java:139)
> {code|
> Everywhere we rely on master connection being up. Instead try using the test Connection
... see how that does. Add timeouts on this flakey test too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message