[
https://issues.apache.org/jira/browse/YARN-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542824#comment-15542824
]
Eric Badger commented on YARN-5700:
-----------------------------------
testAMRestartNotLostContainerCompleteMsg times out intermittently in
branch-2.8, but also intermittently increases the runtime of the test in
branch-2 and trunk by ~10 seconds. These phenomena can be reproduced reliably
by adding a {{Thread.sleep(10)}} to the code as shown below. A sleep as low as
1ms seems to trigger the race condition, though it isn't 100% reliable for
failure at a sleep value that low.
{noformat}
771 // container complete
772 nm1.nodeHeartbeat(
773 am1.getApplicationAttemptId(), 2, ContainerState.COMPLETE);
774 Thread.sleep(10);
775 rm1.waitForState(nm1, containerId2, RMContainerState.COMPLETED);
{noformat}
> testAMRestartNotLostContainerCompleteMsg times out intermittently in 2.8
> ------------------------------------------------------------------------
>
> Key: YARN-5700
> URL: https://issues.apache.org/jira/browse/YARN-5700
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Eric Badger
> Assignee: Eric Badger
>
> {noformat}
> java.lang.Exception: test timed out after 30000 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:301)
> at
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:286)
> at
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:281)
> at
> org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart.testAMRestartNotLostContainerCompleteMsg(TestAMRestart.java:774)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
