All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Francke <Oliver.Francke@filoo.de>
To: Sylvain Munaut <s.munaut@whatever-company.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD memory leak when scrubbing [0.56.6]
Date: Tue, 21 May 2013 17:38:16 +0200	[thread overview]
Message-ID: <519B94E8.9010703@filoo.de> (raw)
In-Reply-To: <CAF6-1L6E6s_wP6012ifwTRwZA4bp5+OLmYo92Y5QbmS20uxReA@mail.gmail.com>

Right,

On 05/21/2013 05:35 PM, Sylvain Munaut wrote:
> Hi,
>
>> subject seems familiar, version was 0.48.3 in the last mail.
>>
>> Not anyone else with perhaps large pg's experiencing such behaviour?
>>
>> Any advice on how to proceed?
> I had the same behavior in both argonaut and bobtail, raising sharply
> ~ 100M or so at each scrub (every 24h).
>
> It's now resolved in cuttlefish AFAICT.
>
> However given the mon leveldb issues I'm having with cuttlefish, I'm
> not sure I'd recommend upgrading ...

not really at this moment. Cause we have an otherwise stable and fast 
cluster for our VM's ;)

Oliver.

>
> Cheers,
>
>      Sylvain


-- 

Oliver Francke

filoo GmbH
Moltkestraße 25a
33330 Gütersloh
HRB4355 AG Gütersloh

Geschäftsführer: S.Grewing | J.Rehpöhler | C.Kunz

Folgen Sie uns auf Twitter: http://twitter.com/filoogmbh

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-05-21 15:38 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 [this message]
2013-05-22  6:21 ` Wolfgang Hennerbichler

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=519B94E8.9010703@filoo.de \
    --to=oliver.francke@filoo.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=s.munaut@whatever-company.com \
    /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.