hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used
Date Wed, 02 Jul 2014 18:57:25 GMT

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

Hudson commented on YARN-2065:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #5808 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5808/])
YARN-2065 AM cannot create new containers after restart (stevel: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1607441)
* /hadoop/common/trunk
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/ContainerManagerImpl.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/TestContainerManagerSecurity.java


> 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
>             Fix For: 2.5.0
>
>         Attachments: YARN-2065-002.patch, YARN-2065-003.patch, 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