hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miklos Szegedi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-7715) Support NM promotion/demotion of running containers.
Date Wed, 16 May 2018 16:35:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477692#comment-16477692
] 

Miklos Szegedi edited comment on YARN-7715 at 5/16/18 4:34 PM:
---------------------------------------------------------------

[~yangjiandan], none of these are the job of this jira. This Jira is about setting the cgroup
based on the setting already propagated to node manager and taken care of. I agree the flag
needs to be in state store, however this has nothing to do with cgroups. Please file a separate
Jira for that. Also I am not convinced that the AM has to be notified about cgroup errors.
cgroup has to be as transparent and failsafe as possible. Any communication to the AM would
just add unnecessary network overhead and probably does not solve the problem. The information
that some cgroup update failed on some node might be interesting to the AM but it is not actionable.


was (Author: miklos.szegedi@cloudera.com):
[~yangjiandan], none of these are the job of this jira. This Jira is about setting the cgroup
based on the setting already propagated to node manager and taken care of. I agree the flag
needs to be in state store, however this has nothing to do with cgroups. Also I am not convinced
that the AM has to be notified about cgroup errors. cgroup has to be as transparent and failsafe
as possible. Any communication to the AM would just add unnecessary network overhead and probably
does not solve the problem. The information that some cgroup update failed on some node might
be interesting to the AM but it is not actionable.

> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message