Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Aaron Staley <aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Serge Hallyn
	<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
	Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>,
	Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: PROBLEM: Processes writing large files in memory-limited LXC container are killed by OOM
Date: Fri, 28 Jun 2013 18:52:41 +0000	[thread overview]
Message-ID: <20130628185241.GA27358@mail.hallyn.com> (raw)
In-Reply-To: <CAMcjixZtW0KdAmLXyDoGFqL2qh4aEgdGjBYJWrPESFMz0dvELw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Quoting Aaron Staley (aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org):
> Hi Serge,
> 
> Thanks a lot. Would you know of any workarounds outside of forcing every
> write to sync to disk (which kills performance)? Perhaps some settings in
> the container I can set?  Unfortunately, modifying dirty_background_ratio
>  and dirty_expire_centiseconds globally (/etc/sysctl.conf) as suggested by
> the serverfault answer will not stop the OOM kills.

Sorry i haven't replied yet have I - no, I'm afraid I don't have any
good ideas offhand.  I think this is something that's going to have
to be fixed in the kernel, and there's really nothing you can do
in the container.  I could be wrong.

Over the next few days I'm going to be taking a fresh look at the
behaviors of the various controllers (at least as documented) for
the sake of thinking about configuration api - perhaps the answer
will become clear to me as I do that.

-serge

  parent reply	other threads:[~2013-06-28 18:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25  5:45 PROBLEM: Processes writing large files in memory-limited LXC container are killed by OOM Aaron Staley
     [not found] ` <CAMcjixYa-mjo5TrxmtBkr0MOf+8r_iSeW5MF4c8nJKdp5m+RPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-25 13:24   ` Serge Hallyn
2013-06-25 20:54     ` Aaron Staley
     [not found]       ` <CAMcjixZtW0KdAmLXyDoGFqL2qh4aEgdGjBYJWrPESFMz0dvELw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27  5:12         ` Zhu Yanhai
     [not found]           ` <CAC8teKXNof5PdU2dMz4iZ8tM=Dx=aZ0efxotDhdc-xopeK-+Xg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27  5:19             ` Aaron Staley
     [not found]               ` <CAMcjixZdXWGezcVQPPo3M0yNBx4TtbiOoqYJQWvNbTyqULifUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 20:51                 ` Aristeu Rozanski
2013-07-01 15:21                 ` Serge Hallyn
2013-07-01 15:27                   ` Aaron Staley
2013-06-28 18:52         ` Serge E. Hallyn [this message]
2013-07-01 18:01   ` Serge Hallyn
2013-07-01 18:45     ` Johannes Weiner
     [not found]     ` <20130701184503.GG17812@cmpxchg.org>
     [not found]       ` <20130701184503.GG17812-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2013-07-01 18:51         ` Aaron Staley
2013-07-01 19:02         ` Serge Hallyn
2013-07-02 12:42           ` 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=20130628185241.GA27358@mail.hallyn.com \
    --to=serge-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
    --cc=aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@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