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 "Yang Wang (JIRA)" <ji...@apache.org> on 2017/12/08 08:44:00 UTC
[jira] [Updated] (YARN-6589) Recover all resources when NM restart
[ https://issues.apache.org/jira/browse/YARN-6589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yang Wang updated YARN-6589:
----------------------------
Attachment: YARN-6589.002.patch
The constructor in ContainerImpl has change, we do not need to recover resource. Because we will get resource from containerTokenIdentifier. And containerTokenIdentifier could be recovered properly.
So i update the patch and just add a test for this case.
> Recover all resources when NM restart
> -------------------------------------
>
> Key: YARN-6589
> URL: https://issues.apache.org/jira/browse/YARN-6589
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Blocker
> Attachments: YARN-6589-YARN-3926.001.patch, YARN-6589.001.patch, YARN-6589.002.patch
>
>
> When NM restart, containers will be recovered. However, only memory and vcores in capability have been recovered. All resources need to be recovered.
> {code:title=ContainerImpl.java}
> // resource capability had been updated before NM was down
> this.resource = Resource.newInstance(recoveredCapability.getMemorySize(),
> recoveredCapability.getVirtualCores());
> {code}
> It should be like this.
> {code:title=ContainerImpl.java}
> // resource capability had been updated before NM was down
> // need to recover all resources, not only <mem, vcores>
> this.resource = Resources.clone(recoveredCapability);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org