[HDDS-10443] Time out in testContainerStateMachineIdempotency

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Component/s: test
• Assignee: Raju Balpande
• Reporter: Siyao Meng
• Created: 29/Feb/24 23:53
• Updated: 08/Apr/24 21:12
• Resolved: 08/Apr/24 21:12

Description

Found in post commit CI:
https://github.com/apache/ozone/actions/runs/8103491257/job/22148698509

[INFO] Running org.apache.hadoop.ozone.TestContainerStateMachineIdempotency
Error:  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 323.224 s <<< FAILURE! - in org.apache.hadoop.ozone.TestContainerStateMachineIdempotency
Error:  org.apache.hadoop.ozone.TestContainerStateMachineIdempotency.testContainerStateMachineIdempotency  Time elapsed: 300.025 s  <<< ERROR!
java.util.concurrent.TimeoutException: testContainerStateMachineIdempotency() timed out after 300 seconds
	at java.util.ArrayList.forEach(ArrayList.java:1259)
	at java.util.ArrayList.forEach(ArrayList.java:1259)
	Suppressed: java.io.IOException: Failed to execute command cmdType: WriteChunk
containerID: 1
datanodeUuid: "c686daf4-14de-466f-a1f0-190f2aa7d41d"
writeChunk {
...

Could either be that the test genuinely takes a long time, or the test cluster is stuck.