[
https://issues.apache.org/jira/browse/YARN-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476776#comment-16476776
]
Jiandan Yang commented on YARN-7715:
-------------------------------------
Hi， [[email protected]]
Thanks for your reply. I mean AM does not know when NM updates resource failed.
Consider flowing case:
1. AM increase vcore by updateContainer
2. NM update Cgroup failed when executing
CGroupsCpuResourceHandlerImpl#updateContainer
And another question: updated containes need to store, but I did not find
related code in your patch.
> Support NM promotion/demotion of running containers.
> ----------------------------------------------------
>
> Key: YARN-7715
> URL: https://issues.apache.org/jira/browse/YARN-7715
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Miklos Szegedi
> Priority: Major
> Fix For: 3.2.0
>
> Attachments: YARN-7715.000.patch, YARN-7715.001.patch,
> YARN-7715.002.patch, YARN-7715.003.patch, YARN-7715.004.patch
>
>
> In YARN-6673 and YARN-6674, the cgroups resource handlers update the cgroups
> params for the containers, based on opportunistic or guaranteed, in the
> *preStart* method.
> Now that YARN-5085 is in, Container executionType (as well as the cpu, memory
> and any other resources) can be updated after the container has started. This
> means we need the ability to change cgroups params after container start.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
