hm - my servers generally have no swap or better said
only a 500 MB swap-file, they are all virtual machines
in a ESXi cluster
you really do not want a VM swapping
this leads in unusaeable performance
in my case the problem was another process eating up all memory
by user-mistake and my hint is t
I had this same problem with the OOM for a while. Very frustrating to have
to reboot a server to bring it back to life.
I found out the OOM only ran when the swap file was about 99% full. The
servers I had this problem on had 16GB and 24GB of ram, but only 2GB of
swap. I increased the swap on the
Am 13.04.2012 15:47, schrieb Mihamina Rakotomandimby:
> On 04/13/2012 03:17 PM, Reindl Harald wrote:
>> with one single command you can protect processes from get killed
>> i started to run this every 15 minutes to make sure it is also
>> active after restarts
>
> I understand your issue, but is
On 04/13/2012 03:17 PM, Reindl Harald wrote:
with one single command you can protect processes from get killed
i started to run this every 15 minutes to make sure it is also
active after restarts
I understand your issue, but isn'there a configuration way to just limit
the memory usage of MySQL
the following may be useful for most server systems
OOM-killer acts if some process reclaims more and more
memory and the kernel randomly kills unimportant tasks
using hughe memory
in case of a running mysqld the classification "unimportant"
is nearly all time wrong and can cause hughe damage and
