You can configure the kernel OOM killer to prefer killing certain
processes over others (see
http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html),
but if the kernel OOM killer is being invoked, /some/ process is going
to die. Unless you're ok with random processes on your system dying,
you're much better off either decreasing your memory use, or increasing
your available memory.
-j
On 7/26/2016 2:29 AM, MemcachedUser wrote:
Looks like memcached was killed by the kernel because it was consuming
too much memory (came across this in the kernel log). Is there a
setting that allows the memcached process to live even if it wants
more memory (but is denied more memory)?
On Tuesday, July 26, 2016 at 3:20:52 PM UTC+8, MemcachedUser wrote:
I'm running Ubuntu 10.04 LTS, I know it's old but I don't think
that is causing the current issue. I run memcached
(1.4.2-1ubuntu4) with the following command: /usr/bin/memcached-v
-d -m 700 -p 11211 -u nobody -l 127.0.0.1 (Memcached is used by my
Django site to cache db queries). The memcached process stops
every few minutes and I don't see anything in the memcached log
file or syslog. Thanks for any help
--
---
You received this message because you are subscribed to the Google
Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
