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-1886) Exceptions in the RM log while cleaning up app attempt
Date Mon, 31 Mar 2014 17:15:26 GMT

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

Jian He commented on YARN-1886:
-------------------------------

This exception is likely due to RM failed over and was constructing the NMToken with a new
key, but NM had not yet re-synced with RM to get the new key and was still hold the old NMToken
key. If NM re-sync takes arbitrarily long, we may see the situation quite often that new RM
is unable to explicitly communicate with this NM e.g. stop/start AM container on this NM.

> Exceptions in the RM log while cleaning up app attempt
> ------------------------------------------------------
>
>                 Key: YARN-1886
>                 URL: https://issues.apache.org/jira/browse/YARN-1886
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Arpit Gupta
>
> Noticed exceptions in the RM log while HA tests were running where we killed RM/AM/Namnode
etc.
> RM failed over and the new active RM tried to kill the old app attempt and ran into this
exception.



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

Mime
View raw message