[
https://issues.apache.org/jira/browse/HDDS-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816181#comment-16816181
]
Elek, Marton commented on HDDS-1435:
------------------------------------
I found an other test failure in
TestRatisPipelineUtils.testPipelineCreationOnNodeRestart
Which seems to be the same. Uploaded the ci2.log.
> ITestOzoneContractOpen.testOpenFileTwice is flaky
> -------------------------------------------------
>
> Key: HDDS-1435
> URL: https://issues.apache.org/jira/browse/HDDS-1435
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Elek, Marton
> Priority: Major
> Labels: ozone-flaky-test
> Attachments: ci.log, ci2.log
>
>
> It is failed with:
> {code}
> java.lang.Exception: test timed out after 30000 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.test.GenericTestUtils.waitFor(GenericTestUtils.java:382)
> at
> org.apache.hadoop.hdds.scm.pipeline.TestRatisPipelineUtils.waitForPipelines(TestRatisPipelineUtils.java:125)
> at
> org.apache.hadoop.hdds.scm.pipeline.TestRatisPipelineUtils.testPipelineCreationOnNodeRestart(TestRatisPipelineUtils.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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)
> {code}
> Log file is uploaded.
> AFAIK the problem is that RatisPipelineUtils.createPipeline connected to a
> non-leader node.
> But it's not clear for me how is it possible. According to the log (attached)
> the leader election continued after the NonLeaderException. It can be just
> the sign that one datanode was missing from the pipeline...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
