From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: Sylvain Munaut <s.munaut@whatever-company.com>,
Oliver Francke <Oliver.Francke@filoo.de>,
"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 21:29:25 +0200 [thread overview]
Message-ID: <519BCB15.8070502@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1305210841410.30656@cobra.newdream.net>
Am 21.05.2013 17:44, schrieb Sage Weil:
> On Tue, 21 May 2013, Stefan Priebe - Profihost AG wrote:
>> Am 21.05.2013 um 17:35 schrieb Sylvain Munaut <s.munaut@whatever-company.com>:
>>
>>> 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 ...
>>
>> I thought all mon leveldb issues were solved?
>
> Not quite. I'm now able to reproduce the leveldb growth from Mike
> Dawson's trace (thanks!) but we don't have a fix yet.
Oh OK. Is there a tracker id?
> I thought the scrub memory issues were addressed by
> f80f64cf024bd7519d5a1fb2a5698db97a003ce8 in 0.56.4... :(
>
> sage
>
next prev parent reply other threads:[~2013-05-21 19:29 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 [this message]
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
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=519BCB15.8070502@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=Oliver.Francke@filoo.de \
--cc=ceph-devel@vger.kernel.org \
--cc=s.munaut@whatever-company.com \
--cc=sage@inktank.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.