You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bence Kosztolnik (Jira)" <ji...@apache.org> on 2022/12/06 13:27:00 UTC
[jira] [Created] (YARN-11390) TestResourceTrackerService.testNodeRemovalNormally: Shutdown nodes should be 0 now expected: <1> but was: <0>
Bence Kosztolnik created YARN-11390:
---------------------------------------
Summary: TestResourceTrackerService.testNodeRemovalNormally: Shutdown nodes should be 0 now expected: <1> but was: <0>
Key: YARN-11390
URL: https://issues.apache.org/jira/browse/YARN-11390
Project: Hadoop YARN
Issue Type: Bug
Components: yarn
Reporter: Bence Kosztolnik
Assignee: Bence Kosztolnik
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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org