hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5416) TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently due to not wait SchedulerApplicationAttempt to be stopped
Date Wed, 27 Jul 2016 16:27:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395930#comment-15395930

Junping Du commented on YARN-5416:

bq.  This looks like an exact dup of YARN-1468 which you also filed. Are they actually different?
Oh. no. YARN-1468 is a very old jira and out of my radar for some reason (I didn't notice
recent comments from Eric there). I think we can close this as dup of that. What do you think?

bq. Junping Du, is there any reason why we would only add the waitSchedulerApplicationAttemptStopped
call for the first app attempt, but not for the subsequent ones?
Hi Eric, this is just following the pattern we applied in YARN-4968 which seems only necessary
to wait before launch another AM immediately - that is exactly where the exception happens.
Do you think there are other places we should add?

> TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently due to not
wait SchedulerApplicationAttempt to be stopped
> ------------------------------------------------------------------------------------------------------------------------------------
>                 Key: YARN-5416
>                 URL: https://issues.apache.org/jira/browse/YARN-5416
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: test, yarn
>            Reporter: Junping Du
>            Assignee: Junping Du
>            Priority: Minor
>         Attachments: YARN-5416.patch
> The test failure stack is:
> Running org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
> Tests run: 54, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 385.338 sec <<<
FAILURE! - in org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
> testRMRestartWaitForPreviousAMToFinish[0](org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart)
 Time elapsed: 43.134 sec  <<< FAILURE!
> java.lang.AssertionError: AppAttempt state is not correct (timedout) expected:<ALLOCATED>
but was:<SCHEDULED>
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at org.junit.Assert.failNotEquals(Assert.java:743)
> 	at org.junit.Assert.assertEquals(Assert.java:118)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:86)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:594)
> 	at org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.launchAM(TestRMRestart.java:1008)
> 	at org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartWaitForPreviousAMToFinish(TestRMRestart.java:530)
> This is due to the same issue that partially fixed in YARN-4968

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message