[
https://issues.apache.org/jira/browse/YARN-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476852#comment-16476852
]
Miklos Szegedi commented on YARN-7715:
--------------------------------------
updateContainer only supports execution type updates so far. A vcore increase
or decrease does not trigger it. I agree, it should. This Jira was about
promotion, that one is about resource change. Would you like to file a JIRA?
Do you mean state store in the second case? I think that is legit, however it
is also out of the scope of this patch. [~haibochen], [~asuresh], what do you
think? Do we need/have the opportunistic flag in state store?
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
