All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: cgroups to prevent OSD from taking down a whole machine
Date: Fri, 08 Feb 2013 15:46:38 +0100	[thread overview]
Message-ID: <51150FCE.7050501@widodh.nl> (raw)

Hi,

Has anybody tried this yet?

Running into the memory leaks during scrubbing[0] I started thinking 
about a way to limit OSDs to a specific amount of memory.

A machine has 32GB of memory, 4 OSDs, so you might want to limit each 
OSD to 8GB so it can't take the whole machine down and would only kill 
itself.

I think I'll give it a try on a couple of machines, but I just wanted to 
see if anybody has tried this already or sees any downsides to this?

We use cgroups in the CloudStack project (through libvirt) to prevent 
that a memory leak in one KVM proces can take down a whole hypervisor, 
it works pretty well there.

Suggestions or comments?

Wido

[0]: http://tracker.ceph.com/issues/3883

             reply	other threads:[~2013-02-08 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 14:46 Wido den Hollander [this message]
2013-02-08 14:52 ` cgroups to prevent OSD from taking down a whole machine Mark Nelson
2013-02-08 14:58   ` Andrey Korolyov
2013-02-08 14:55 ` Andrey Korolyov

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=51150FCE.7050501@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.