You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:11 UTC
[jira] [Updated] (HDDS-1435)
ITestOzoneContractOpen.testOpenFileTwice is flaky
[ https://issues.apache.org/jira/browse/HDDS-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-1435:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> ITestOzoneContractOpen.testOpenFileTwice is flaky
> -------------------------------------------------
>
> Key: HDDS-1435
> URL: https://issues.apache.org/jira/browse/HDDS-1435
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: test
> Reporter: Marton Elek
> Priority: Major
> Labels: TriagePending, 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org