You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2015/02/09 22:24:35 UTC

[jira] [Commented] (YARN-3161) Containers' information are lost in some cases when RM restart

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

Jian He commented on YARN-3161:
-------------------------------

bq. 1. NM restarts before it sends containers' information to the new active RM. 
Work-preserving NM restart is supposed to be enabled to persist containers across NM restart 
bq.  NM stops and it could not send containers' information to the new active RM.
If we want to retrieve back these containers, I don't think we can do anything other than persisting the containers, which is what we wanted to avoid.

> Containers' information are lost in some cases when RM restart
> --------------------------------------------------------------
>
>                 Key: YARN-3161
>                 URL: https://issues.apache.org/jira/browse/YARN-3161
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Jun Gong
>
> When RM restart, containers' information will be lost for the following scenarios:
> 1. NM restarts before it sends containers' information to the new active RM. 
> 2. NM stops and it could not send containers' information to the new active RM.
> Without those containers' information, corresponding AM will never get their status through RM, and AM would just wait them for ever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)