From: "Arkadiusz Miśkiewicz" <arekm-evZBlRFTdvA@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: cgroup memory limit problems
Date: Wed, 9 Nov 2011 21:57:06 +0100 [thread overview]
Message-ID: <201111092157.06819.arekm@maven.pl> (raw)
Hi,
I have a machine with 6GB of ram and a cgroup for apache processes limited to
memory.limit_in_bytes = "5100M";
memory.soft_limit_in_bytes = "5000M";
Unfortunately when apache processes ate all ram assigned to their cgroup load
on whole machine jumps the roof.
cgroup aware OOM kicks in, kills one process and that doesn't help.
If I'm fast enough I notice and then apache processes require tons of kill -9
(I'm doing "killall -9 apache" in a while (true) loop for 20-30s) to get
killed (and that not always succeeds - sometimes I'm unable to kill these and
I'm just doing sysrq u, s, b after few minutes.. if I'm lucky. Sometimes I
cannot do any command).
This all happens on 2.6.38.8 kernel.
http://ixion.pld-linux.org/~arekm/cgroup-eaten-memory-failure-1.txt
for kernel log. It ends with reboot of the machine.
Now the question is - is this is how cgroup memory limit supposed to work? If
yes then it's hardly usable but maybe there are some patches for this?
Would newer kernels be better ? (cannot test immediately since newer kernels
kill ipmi connectivity on that machine). I would expect apache processes to be
killed without taking down entire machine.
ps. found similar history at http://serverfault.com/questions/211509/how-to-
stop-apache-from-crashing-my-entire-server from year ago
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
next reply other threads:[~2011-11-09 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 20:57 Arkadiusz Miśkiewicz [this message]
[not found] ` <201111092157.06819.arekm-evZBlRFTdvA@public.gmane.org>
2011-11-09 22:45 ` cgroup memory limit problems Daniel Lezcano
[not found] ` <4EBB026D.8090701-GANU6spQydw@public.gmane.org>
2011-11-09 23:01 ` Arkadiusz Miśkiewicz
2011-11-09 22:51 ` Balbir Singh
[not found] ` <CAKTCnzmHk1U6fP+jrw2Rq3dLwU30gyocRBp2QpQVHAbU=x5uSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-09 22:53 ` Balbir Singh
2011-11-09 22:58 ` Arkadiusz Miśkiewicz
[not found] ` <201111092358.58079.arekm-evZBlRFTdvA@public.gmane.org>
2011-11-10 0:10 ` KAMEZAWA Hiroyuki
[not found] ` <20111110091012.0ce7d719.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2011-11-18 9:13 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201111092157.06819.arekm@maven.pl \
--to=arekm-evzblrftdva@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox