[
https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129309#comment-15129309
]
MENG DING commented on YARN-4599:
---------------------------------
[~aw]:
bq. We need this as something that can be set and I'd propose that the default
be off given that administrators are going to be very confused when they see
container usage go above the limit.
I thought the container process will be paused by the OOM controller when the
limit is reached, so why will the memory usage go above the limit?
> Set OOM control for memory cgroups
> ----------------------------------
>
> Key: YARN-4599
> URL: https://issues.apache.org/jira/browse/YARN-4599
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.9.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
>
> YARN-1856 adds memory cgroups enforcing support. We should also explicitly
> set OOM control so that containers are not killed as soon as they go over
> their usage. Today, one could set the swappiness to control this, but
> clusters with swap turned off exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
