All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Hennerbichler <wolfgang.hennerbichler@risc-software.at>
To: Oliver Francke <Oliver.Francke@filoo.de>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD memory leak when scrubbing [0.56.6]
Date: Wed, 22 May 2013 08:21:18 +0200	[thread overview]
Message-ID: <519C63DE.7070404@risc-software.at> (raw)
In-Reply-To: <519B9196.5090402@filoo.de>



On 05/21/2013 05:24 PM, Oliver Francke wrote:
> Well,

> 
> Not anyone else with perhaps large pg's experiencing such behaviour?

100pg's per pool, 3 pools. deep-scrub adds about 200M to every OSD, it
get's worse in time. it gets better when using syslog instead of direct
logging, interestingly enougy.

> Any advice on how to proceed?

in my cast it is: wait until they say: the cuttlefish swims into a
stable direction. and restart osd's every now and then...

> Thnx in advance,
> 
> Oliver.
> 


-- 
DI (FH) Wolfgang Hennerbichler
Software Development
Unit Advanced Computing Technologies
RISC Software GmbH
A company of the Johannes Kepler University Linz

IT-Center
Softwarepark 35
4232 Hagenberg
Austria

Phone: +43 7236 3343 245
Fax: +43 7236 3343 250
wolfgang.hennerbichler@risc-software.at
http://www.risc-software.at

      parent reply	other threads:[~2013-05-22  6:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 15:24 OSD memory leak when scrubbing [0.56.6] Oliver Francke
2013-05-21 15:34 ` Oliver Francke
2013-05-21 15:35 ` Sylvain Munaut
2013-05-21 15:37   ` Stefan Priebe - Profihost AG
2013-05-21 15:44     ` Sage Weil
2013-05-21 16:04       ` Mike Dawson
2013-05-21 19:29       ` Stefan Priebe
2013-05-21 19:31         ` Sage Weil
2013-05-21 19:38           ` Oliver Francke
2013-05-21 15:38   ` Oliver Francke
2013-05-22  6:21 ` Wolfgang Hennerbichler [this message]

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=519C63DE.7070404@risc-software.at \
    --to=wolfgang.hennerbichler@risc-software.at \
    --cc=Oliver.Francke@filoo.de \
    --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.