[HDDS-9962] Intermittent timeout in TestBlockDeletion.testBlockDeletion

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0.0, 1.4.1
• Component/s: SCM
• Labels: pull-request-available
• Assignee: ChenXi
• Reporter: Attila Doroszlai
• Created: 19/Dec/23 06:37
• Updated: 06/May/24 18:03
• Resolved: 29/Dec/23 15:36

Description

https://github.com/adoroszlai/ozone-build-results/blob/master/2023/12/19/27706/it-ozone/hadoop-ozone/integration-test/org.apache.hadoop.ozone.container.common.statemachine.commandhandler.TestBlockDeletion.txt

Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 248.0 s <<< FAILURE! -- in org.apache.hadoop.ozone.container.common.statemachine.commandhandler.TestBlockDeletion
org.apache.hadoop.ozone.container.common.statemachine.commandhandler.TestBlockDeletion.testBlockDeletion(ReplicationConfig)[1] -- Time elapsed: 47.02 s <<< ERROR!
java.util.concurrent.TimeoutException: 
  ...
  at org.apache.ozone.test.GenericTestUtils.waitFor(GenericTestUtils.java:230)
  at org.apache.hadoop.ozone.container.common.statemachine.commandhandler.TestBlockDeletion.testBlockDeletion(TestBlockDeletion.java:302)

Issue Links

• fixes: HDDS-10799 SCMBlockDeletingService stuck in PAUSING state
• is related to: HDDS-8882 Add state management of SCM's DeleteBlocksCommand to avoid sending duplicate delete transactions to the DN
• relates to: HDDS-9976 Ozone StateContext Memory leak for DeleteBlocksCommand when queue is full
• relates to: HDDS-8223 SCM delete block service shoud run wait for safemode to exit.
• links to: GitHub Pull Request #5886