You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Daan Hoogland (JIRA)" <ji...@apache.org> on 2015/07/28 00:27:04 UTC
[jira] [Commented] (CLOUDSTACK-8678) OOM Kills Guests
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643525#comment-14643525 ]
Daan Hoogland commented on CLOUDSTACK-8678:
-------------------------------------------
Josh, this seems more a user question then a bug report;) It could well be or become one though. What you are looking for is the overprovisioning ratio, i think. set it to 0.9 or some other value below 1. I am not sure that ACS honours it correctly but it is worth a shot. look for overprovisioning in the global settings (or zone/pod/cluster settings)
> OOM Kills Guests
> ----------------
>
> Key: CLOUDSTACK-8678
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8678
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Hypervisor Controller, KVM
> Affects Versions: 4.4.2
> Environment: Intel Xeon Quad Core CPU L5520 @ 2.27GHz
> 98 GB RAM
> Ubuntu 14.04
> Running Cloustack 4.4.2
> Reporter: Josh Harshman
> Priority: Critical
>
> We have several KVM nodes running Cloudstack 4.4.2. Sometimes an instance with X amount of RAM provisioned will be started on a host that has X+a small amount of RAM free. The kernel OOM killer will eventually kill off the instance. Has anyone else seen this behavior, is there a way to reserve RAM for use by the host instead of by Cloudstack? Looking at the numbers in the database and the logs, Cloudstack is trying to use 100% of the RAM on the host.
> Any thoughts would be appreciated.
> Thank you,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)