[
https://issues.apache.org/jira/browse/YARN-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372975#comment-15372975
]
Jason Lowe commented on YARN-5317:
----------------------------------
Thanks for the patch, [~sandflee]!
Also I noticed the same code snippet appears in
testAMRestartWithExistingContainers, so I'm wondering if it could have the same
issue. There are also other places that don't have the exact same code snippet
but are waiting for an app state of ACCEPTED then doing things relative to the
app attempt, so I'm thinking they too could be susceptible to the
app-is-accepted-but-attempt-not-scheduled race.
> testAMRestartNotLostContainerCompleteMsg may fail
> -------------------------------------------------
>
> Key: YARN-5317
> URL: https://issues.apache.org/jira/browse/YARN-5317
> Project: Hadoop YARN
> Issue Type: Test
> Reporter: sandflee
> Assignee: sandflee
> Priority: Minor
> Attachments: YARN-5317.01.patch
>
>
> 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:261)
> at
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:225)
> at
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:207)
> at
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:746)
> at
> org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart.testAMRestartNotLostContainerCompleteMsg(TestAMRestart.java:841)
> see
> https://builds.apache.org/job/PreCommit-YARN-Build/12204/testReport/org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager/TestAMRestart/testAMRestartNotLostContainerCompleteMsg/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
