From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Joao Eduardo Luis <joao.luis@inktank.com>
Cc: "Travis Rhoden" <trhoden@gmail.com>,
"Sébastien Han" <han.sebastien@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: mon memory leak
Date: Wed, 13 Mar 2013 15:06:11 +0100 [thread overview]
Message-ID: <514087D3.20200@profihost.ag> (raw)
In-Reply-To: <514085F5.6010509@inktank.com>
Hi Joao,
Am 13.03.2013 14:58, schrieb Joao Eduardo Luis:
> I'm expecting to be able to find the time Real Soon Now to put a doc
> together with ways, for anyone willing, to provide us further insight on
> what's happening. The monitor is supposed to be able to dump a heap
> profile (using gperftools) on-the-fly, but I recall having some issues
> with that not so long ago, so that's probably one thing to look into asap.
Thanks - that would be great i'm willing ;-)
> In any case, Stefan, do you by chance still have that monitor going?
Sadly not i needed the memory ;-)
> Furthermore, assuming you are using a
> version prior to v0.58,
Yes current Bobtail 0.56.3
> any chance you can run a 'du -chs
> /var/lib/ceph/mon/ceph-foo',
No idea what you expect to see but all mon servers consume 180MB of disk
space.
[: ~]# du -chs /ceph/mon
180M /ceph/mon
180M total
Greets,
Stefan
next prev parent reply other threads:[~2013-03-13 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 10:44 mon memory leak Stefan Priebe - Profihost AG
2013-03-13 11:02 ` Sébastien Han
2013-03-13 13:42 ` Travis Rhoden
2013-03-13 13:58 ` Joao Eduardo Luis
2013-03-13 14:06 ` Stefan Priebe - Profihost AG [this message]
2013-03-13 14:16 ` Joao Eduardo Luis
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=514087D3.20200@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=han.sebastien@gmail.com \
--cc=joao.luis@inktank.com \
--cc=trhoden@gmail.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.