2017-12-16 20:27 UTC

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0014172CentOS-7-OTHERpublic2017-11-23 22:00
Reporterhector 
PriorityhighSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformAmazon AWS - KubernetesOSCentOS7OS Version
Product Version7.4.1708 
Target VersionFixed in Version 
Summary0014172: oom crashes the machine
DescriptionI am running a Kubernetes cluster composed of CentOS-7 machines. I detected that whenever the cgroup where the kubernetes pods & kubelet cannot allocate more memory. The machine crashes. It seems to be related to an oom error that crashes the Kernel.

I tried to set `vm.overcommit_memory=1` or to `2` but I get the same result. I followed what suggested in this page https://docs.openshift.org/latest/admin_guide/overcommit.html. But I believe there should be something else to configure when using CentOS.

Primarily I'd like to avoid my machine to crash due to this oom problem. How can I achieve this contention ?

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"

KERNEL_VERSION=3.10.0-693.5.2.el7.x86_64

Thanks
Steps To ReproduceI create process inside one cgroup allocating more memory that the one available for this cgroup.
Additional InformationThis issue could be related to https://lists.centos.org/pipermail/centos/2012-May/126089.html. I also tried what it was mentioned in this issue without any success.
TagsNo tags attached.
abrt_hash
URL
Attached Files

-Relationships
+Relationships

-Notes
There are no notes attached to this issue.
+Notes

-Issue History
Date Modified Username Field Change
2017-11-23 22:00 hector New Issue
+Issue History