hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used
Date Sat, 24 May 2014 05:30:02 GMT

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

Jian He commented on YARN-2065:
-------------------------------

Also changed authorizeGetAndStopContainerRequest to check against appId.
bq. The token is generated with the previous container's attempt Id, instead of the current
attemptId.
This actually should not be a problem after changing the two methods to check against appId
instead of attemptId.



> AM cannot create new containers after restart-NM token from previous attempt used
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-2065
>                 URL: https://issues.apache.org/jira/browse/YARN-2065
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Steve Loughran
>            Assignee: Jian He
>         Attachments: YARN-2065.1.patch
>
>
> Slider AM Restart failing (SLIDER-34). The AM comes back up, but it cannot create new
containers.
> The Slider minicluster test {{TestKilledAM}} can replicate this reliably -it kills the
AM, then kills a container while the AM is down, which triggers a reallocation of a container,
leading to this failure.



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

Mime
View raw message