hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi OZAWA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2483) TestAMRestart#testShouldNotCountFailureToMaxAttemptRetry fails due to incorrect AppAttempt state
Date Sat, 30 Aug 2014 16:43:54 GMT

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

Tsuyoshi OZAWA commented on YARN-2483:
--------------------------------------

Maybe the test failure is because of following line, but I don't have any good idea to avoid
it for now...:
{code}
  private static final class AMContainerAllocatedTransition
      implements
      MultipleArcTransition<RMAppAttemptImpl, RMAppAttemptEvent, RMAppAttemptState>
{
    @Override
    public RMAppAttemptState transition(RMAppAttemptImpl appAttempt,
        RMAppAttemptEvent event) {
     ...
     // Note that YarnScheduler#allocate is not guaranteed to be able to
      // fetch it since container may not be fetchable for some reason like
      // DNS unavailable causing container token not generated. As such, we
      // return to the previous state and keep retry until am container is
      // fetched.
      if (amContainerAllocation.getContainers().size() == 0) {
        appAttempt.retryFetchingAMContainer(appAttempt);
        return RMAppAttemptState.SCHEDULED;
      }
{code}

> TestAMRestart#testShouldNotCountFailureToMaxAttemptRetry fails due to incorrect AppAttempt
state
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2483
>                 URL: https://issues.apache.org/jira/browse/YARN-2483
>             Project: Hadoop YARN
>          Issue Type: Test
>            Reporter: Ted Yu
>
> From https://builds.apache.org/job/Hadoop-Yarn-trunk/665/console :
> {code}
> testShouldNotCountFailureToMaxAttemptRetry(org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart)
 Time elapsed: 49.686 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:84)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:417)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAM(MockRM.java:582)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAndRegisterAM(MockRM.java:589)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForNewAMToLaunchAndRegister(MockRM.java:182)
> 	at org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart.testShouldNotCountFailureToMaxAttemptRetry(TestAMRestart.java:402)
> {code}
> TestApplicationMasterLauncher#testallocateBeforeAMRegistration fails with similar cause.
> These tests failed in build #664 as well.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message