[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644256#comment-14644256
 ] 

Daan Hoogland edited comment on CLOUDSTACK-8678 at 7/28/15 9:13 PM:
--------------------------------------------------------------------

clear. there are some other knobs to turn: vm.memballoon.disable in the 
agent.properties file on the host(s) and 
cluster.memory.allocated.capacity.notificationthreshold and 
cluster.memory.allocated.capacity.disablethreshold. I had some chats about them 
and came to the conclusion that these might help you to some extend, Let's use 
this ticket to come to additional functional demands. [~jharshman] Can you 
investigate those settings to see if these are good enough for you or we need 
more/better/other things?


was (Author: dahn):
clear. there are some other knobs to turn: vm.memballoon.disable in the 
agent.properties file on the host(s) and 
cluster.memory.allocated.capacity.notificationthreshold and 
cluster.memory.allocated.capacity.disablethreshold. I had some chats about them 
and came to the conclusion that these might help you to some extend, Let's use 
this ticket to come to additional functional demands.

> 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)

Reply via email to