[HDDS-1435] TestRatisPipelineUtils.testPipelineCreationOnNodeRestart is flaky

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: test
• Labels: TriagePending ozone-flaky-test
• Target Version/s: 1.4.0
• Sprint: HDDS BadLands
• Assignee: Unassigned
• Reporter: Marton Elek
• Created: 12/Apr/19 11:13
• Updated: 09/Oct/23 13:32
• Resolved: 09/Oct/23 13:32

Description

It is failed with:

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)

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...

Issue Links

• is duplicated by: HDDS-1808 TestRatisPipelineCreateAndDestory#testPipelineCreationOnNodeRestart times out