[
https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943943#comment-13943943
]
Jian He commented on YARN-556:
------------------------------
IMO, I would prefer work from the protocol changes first, RM can choose to
ignore the container statuses reports for the time being. It's not able to test
on a real cluster if we make scheduler changes only, since there are no real
entities to report the container statuses. If possible, I'd like this happen on
trunk since this can be deeply coupled inside RM, we can catch bugs as early as
possible and also avoid the merge nightmare. Thoughts?
> RM Restart phase 2 - Work preserving restart
> --------------------------------------------
>
> Key: YARN-556
> URL: https://issues.apache.org/jira/browse/YARN-556
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: resourcemanager
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: Work Preserving RM Restart.pdf
>
>
> YARN-128 covered storing the state needed for the RM to recover critical
> information. This umbrella jira will track changes needed to recover the
> running state of the cluster so that work can be preserved across RM restarts.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
