[
https://issues.apache.org/jira/browse/YARN-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062060#comment-14062060
]
Jason Lowe commented on YARN-2152:
----------------------------------
Yeah that's what I suspected as well, but I wanted to mention it in case I
missed something. It's crucial we get the token compatibility sorted out
sooner rather than later, otherwise I can see us regularly breaking
compatibility between even minor versions as we tweak tokens to add features.
Whenever that happens rolling upgrades will not work in practice.
> Recover missing container information
> -------------------------------------
>
> Key: YARN-2152
> URL: https://issues.apache.org/jira/browse/YARN-2152
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Jian He
> Assignee: Jian He
> Fix For: 2.5.0
>
> Attachments: YARN-2152.1.patch, YARN-2152.1.patch, YARN-2152.2.patch,
> YARN-2152.3.patch
>
>
> Container information such as container priority and container start time
> cannot be recovered because NM container today lacks such container
> information to send across on NM registration when RM recovery happens
--
This message was sent by Atlassian JIRA
(v6.2#6252)
