[
https://issues.apache.org/jira/browse/YARN-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594858#comment-16594858
]
Jiandan Yang edited comment on YARN-8717 at 9/7/18 3:05 AM:
-------------------------------------------------------------
Hi [~cheersyang]
Thanks for watching.
We found NM was killed by OOM-killer.
conditions are as follows:
```
yarn.nodemanager.resource.memory.enforced=false
yarn.nodemanager.resource.memory-mb = 100G
Physical Memory of NM machine is 120G
NM has two container, each requests 40G memory, but actual each request 50G+
```
So we thought setting limit on the hireachy of hadoop-yarn
was (Author: yangjiandan):
Hi [~cheersyang]
Thanks for watching.
We found NM was killed by OOM-killer.
conditions are as follows:
```
yarn.nodemanager.resource.memory.enabled=false
yarn.nodemanager.resource.memory-mb = 100G
Physical Memory of NM machine is 120G
NM has two container, each requests 40G memory, but actual each request 50G+
```
So we thought setting limit on the hireachy of hadoop-yarn
> set memory.limit_in_bytes when NodeManager starting
> ---------------------------------------------------
>
> Key: YARN-8717
> URL: https://issues.apache.org/jira/browse/YARN-8717
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Jiandan Yang
> Assignee: Jiandan Yang
> Priority: Major
> Labels: cgroups
> Attachments: YARN-8717.001.patch
>
>
> CGroupsCpuResourceHandlerImpl sets cpu quota at hirarchy of hadoop-yarn to
> restrict total resource of cpu of NM when NM starting;
> CGroupsMemoryResourceHandlerImpl also should set memory.limit_in_bytes at
> hirachy of hadoop-yarn to control memory resource of NM
--
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
