From: Oliver Francke <Oliver.Francke@filoo.de>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: OSD memory leak when scrubbing [0.56.6]
Date: Tue, 21 May 2013 17:24:06 +0200 [thread overview]
Message-ID: <519B9196.5090402@filoo.de> (raw)
Well,
subject seems familiar, version was 0.48.3 in the last mail.
Some more of the story. Before successful upgrade to latest bobtail
everything with regards to scrubbing was disabled.
That is via:
ceph osd tell \* injectargs '--osd-max-scrubs 0'
We are running fine now since 9th of may. Fine means though, not have
ran any scrubbing for ages.
This morning I re-started scrubbing. After a couple of hours I detected
the first OSD's eating up memory.
Top-scorer was running with 23GiB rss. After stopping scrubbing again
there was no regain of memory.
Not anyone else with perhaps large pg's experiencing such behaviour?
Any advice on how to proceed?
Thnx in advance,
Oliver.
--
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
next reply other threads:[~2013-05-21 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 15:24 Oliver Francke [this message]
2013-05-21 15:34 ` OSD memory leak when scrubbing [0.56.6] 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
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=519B9196.5090402@filoo.de \
--to=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.