[YARN-11390] TestResourceTrackerService.testNodeRemovalNormally: Shutdown nodes should be 0 now expected: <1> but was: <0>

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 3.3.6
• Fix Version/s: 3.4.0, 3.2.5, 3.3.6
• Component/s: yarn
• Labels: pull-request-available
• Target Version/s: 3.4.0, 3.3.6
• Hadoop Flags: Reviewed
• Assignee: Bence Kosztolnik
• Reporter: Bence Kosztolnik
• Created: 06/Dec/22 13:26
• Updated: 28/Jan/24 02:05
• Resolved: 08/Dec/22 18:36

Description

Some times the TestResourceTrackerService.testNodeRemovalNormally fails with the following message

java.lang.AssertionError: Shutdown nodes should be 0 now expected:<1> but was:<0>
at org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService.testNodeRemovalUtilDecomToUntracked(TestResourceTrackerService.java:1723)
at org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService.testNodeRemovalUtil(TestResourceTrackerService.java:1685)
at org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService.testNodeRemovalNormally(TestResourceTrackerService.java:1530)

This can happen in case if the hardcoded 1s sleep in the test not enough for proper shut down.

To fix this issue we should poll the cluster status with a time out, and see the cluster can reach the expected state

Issue Links

• links to: GitHub Pull Request #5190