You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/02/05 21:31:00 UTC
[jira] [Resolved] (HBASE-19907) TestMetaWithReplicas still flakey
[ https://issues.apache.org/jira/browse/HBASE-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-19907.
---------------------------
Resolution: Fixed
Resolving. HBASE-19931 has taken up the baton on the new failure types for TestMetaWithReplicas. Pushed to branch-2 and master.
> TestMetaWithReplicas still flakey
> ---------------------------------
>
> Key: HBASE-19907
> URL: https://issues.apache.org/jira/browse/HBASE-19907
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19907.master.001.patch
>
>
> Still fails because all meta replicas arrive at same server even though supposedly protection against this added by me in HBASE-19840.
> -------------------------------------------------------------------------------
> Test set: org.apache.hadoop.hbase.client.TestMetaWithReplicas
> -------------------------------------------------------------------------------
> Tests run: 5, Failures: 0, Errors: 2, Skipped: 1, Time elapsed: 600.251 s <<< FAILURE! - in org.apache.hadoop.hbase.client.TestMetaWithReplicas
> org.apache.hadoop.hbase.client.TestMetaWithReplicas Time elapsed: 563.656 s <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 600 seconds
> at org.apache.hadoop.hbase.client.TestMetaWithReplicas.shutdownMetaAndDoValidations(TestMetaWithReplicas.java:255)
> at org.apache.hadoop.hbase.client.TestMetaWithReplicas.testShutdownHandling(TestMetaWithReplicas.java:181)
> org.apache.hadoop.hbase.client.TestMetaWithReplicas Time elapsed: 563.656 s <<< ERROR!
> java.lang.Exception: Appears to be stuck in thread NIOServerCxn.Factory:0.0.0.0/0.0.0.0:49912
> The move of hbase:meta actually moves it back to same server.... no good.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)