hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11524) TestReplicaWithCluster#testChangeTable and TestReplicaWithCluster#testCreateDeleteTable fail
Date Wed, 16 Jul 2014 09:51:04 GMT

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

Mikhail Antonov commented on HBASE-11524:
-----------------------------------------

[~tianq] there was kind of intermediate commit to help get more debug logs. See TestReplicaWithCluster
turns zombie – ADDS TIMEOUTS SO CAN DEBUG ZOMBIE (stack: rev 7175f51f0817e93fe2c46aa39937fdff73e383d6)

If you got this commit fetched on your environment, you could pick the patch I attached to
that jira and just apply it on top of this one. After that this test passes for me. The error
seems to be that with recent changes each server holds instance of HConnection, but when we
have 2 miniclusters in the same test, calling #shutdown() on any of them closes all connections
in JVM, for both miniclusters.

Let me know if that patch works for you.

> TestReplicaWithCluster#testChangeTable and TestReplicaWithCluster#testCreateDeleteTable
fail
> --------------------------------------------------------------------------------------------
>
>                 Key: HBASE-11524
>                 URL: https://issues.apache.org/jira/browse/HBASE-11524
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Qiang Tian
>
> "git bisect" points to HBASE-11367.
> build server run: (I did not get it in my local test)
> {quote}
> java.lang.Exception: test timed out after 30000 milliseconds
> 	at java.lang.Thread.sleep(Native Method)
> 	at org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:539)
> 	at org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:424)
> 	at org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:1185)
> 	at org.apache.hadoop.hbase.client.TestReplicaWithCluster.testCreateDeleteTable(TestReplicaWithCluster.java:138)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 	at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {quote}
> suspected log messages:
> {quote}
> 2014-07-15 23:52:09,272 INFO  2014-07-15 23:52:09,263 WARN  [PostOpenDeployTasks:44a7fe2589d83138452640fecb7cae80]
handler.OpenRegionHandler$PostOpenDeployTasksThread(326): Exception running postOpenDeployTasks;
region=44a7fe2589d83138452640fecb7cae80
> java.lang.NullPointerException: No connection
> >-at org.apache.hadoop.hbase.MetaTableAccessor.getHTable(MetaTableAccessor.java:180)
> >-at org.apache.hadoop.hbase.MetaTableAccessor.getMetaHTable(MetaTableAccessor.java:193)
> >-at org.apache.hadoop.hbase.MetaTableAccessor.putToMetaTable(MetaTableAccessor.java:941)
> >-at org.apache.hadoop.hbase.MetaTableAccessor.updateLocation(MetaTableAccessor.java:1300)
> >-at org.apache.hadoop.hbase.MetaTableAccessor.updateRegionLocation(MetaTableAccessor.java:1278)
> >-at org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:1724)
> >-at org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler$PostOpenDeployTasksThread.run(OpenRegionHandler.java:321)
> coordination.ZkOpenRegionCoordination(231): Opening of region {ENCODED => 44a7fe2589d83138452640fecb7cae80,
NAME => 'testCreateDeleteTable,,1405493529036_0001.44a7fe2589d83138452640fecb7cae80.',
STARTKEY => '', ENDKEY => '', REPLICA_ID => 1} failed, transitioning from OPENING
to FAILED_OPEN in ZK, expecting version 1
> 2014-07-15 23:52:09,272 INFO  [RS_OPEN_REGION-bdvm101:18352-1] regionserver.HRegion(1239):
Closed testCreateDeleteTable,,1405493529036.8573bc63fc7f328cf926a28f22c0db07.
> 2014-07-15 23:52:09,272 DEBUG [RS_OPEN_REGION-bdvm101:23828-0] zookeeper.ZKAssign(805):
regionserver:23828-0x1473df0c2ef0002, quorum=localhost:61041, baseZNode=/hbase Transitioning
44a7fe2589d83138452640fecb7cae80 from RS_ZK_REGION_OPENING to RS_ZK_REGION_FAILED_OPEN
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message