[
https://issues.apache.org/jira/browse/YARN-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664139#comment-16664139
]
Hudson commented on YARN-8930:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15323 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15323/])
YARN-8930. CGroup-based strict container memory enforcement does not (rkanter:
rev f76e3c3db789dd6866fa0fef8e014cbfe8c8f80d)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/resources/MemoryResourceHandler.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/NodeManagerCGroupsMemory.md
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/resources/TestCGroupsMemoryResourceHandlerImpl.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/monitor/ContainersMonitorImpl.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/linux/resources/CGroupsMemoryResourceHandlerImpl.java
> CGroup-based strict container memory enforcement does not work with
> CGroupElasticMemoryController
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-8930
> URL: https://issues.apache.org/jira/browse/YARN-8930
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.2.0
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-8930.00.patch, YARN-8930.01.patch
>
>
> When yarn.nodemanger.resource.memory.enforced is set to true with memory
> cgroup turned on, (aka strict memory enforcement), containers monitor relies
> on the under_oom status read from the container cgroup's memory.oom_control
> file.
> However, when the root yarn container cgroup is under oom (e.g. when the node
> is overallocating iteself), the under_oom status is set for all yarn
> containers regardless of whether each individual container has run over its
> memory limit.
> What essentially happens is that whenever the root cgroup is under oom, all
> yarn containers are killed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
