From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" 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 Message-ID: <20130628185241.GA27358@mail.hallyn.com> References: <20130625132432.GA4098@sergelap> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Aaron Staley Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Serge Hallyn , Li Zefan , Paul Menage List-Id: containers.vger.kernel.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