From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Travis Rhoden <trhoden@gmail.com>
Cc: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag>,
"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 13:58:13 +0000 [thread overview]
Message-ID: <514085F5.6010509@inktank.com> (raw)
In-Reply-To: <CACkq2mr1juPpqn85jsxeNr_RdgX1nyC6KDLehuNs5rSveWMALw@mail.gmail.com>
On 03/13/2013 01:42 PM, Travis Rhoden wrote:
> Hi Stefan,
>
> I have seen a mon grow quite high on Bobtail. Joao had some theories
> as for why, and I was able to provide him with a memory dump of the
> running process. No word yet on whether it revealed anything, but I
> know it is on his stack. Background here:
> http://thread.gmane.org/gmane.comp.file-systems.ceph.user/14
>
> - Travis
Hi all,
As Travis points out, this has been seen before. I've spent a fair
amount of time chasing this down now, but haven't got to any useful
conclusions yet. Although this is concerning, chasing down this kind of
behaviour tends to be a time sink and there are other more pressing
issues that have been requiring most of my attention. This hasn't been
forgotten and I've been allocating my time to it as possible.
On Sébastien's issue, that may very well be caused by some of the
memleaks that have been fixed some time since argonaut, prior to bobtail.
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.
In any case, Stefan, do you by chance still have that monitor going? If
so, are you able to tell us what's that monitor rank? 'ceph mon_status'
should help you assessing that. Furthermore, assuming you are using a
version prior to v0.58, any chance you can run a 'du -chs
/var/lib/ceph/mon/ceph-foo', with foo being the mem-hogging monitor's
id, and then, if you notice an abnormal disk consumption on one of the
directories, dive in to check where said consumption is happening?
-Joao
>
> On Wed, Mar 13, 2013 at 7:02 AM, Sébastien Han <han.sebastien@gmail.com> wrote:
>>
>> Hi,
>>
>> I do have some ceph-mon memory leak as well but it's on Argonaut.
>>
>> See the memory consumption here:
>> [snipped]
>>
>> Sorry for the long post.
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Wed, Mar 13, 2013 at 11:44 AM, Stefan Priebe - Profihost AG
>> <s.priebe@profihost.ag> wrote:
>>> Hi,
>>>
>>> are there any known ceph-mon memory leaks in bobtail? Today i've seen a
>>> ceph-mon process consuming 50GB Memory.
>>>
>>> Stefan
>>> --
>>> 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
>> --
>> 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
> --
> 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
>
--
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 prev parent reply other threads:[~2013-03-13 13:59 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 [this message]
2013-03-13 14:06 ` Stefan Priebe - Profihost AG
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=514085F5.6010509@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=han.sebastien@gmail.com \
--cc=s.priebe@profihost.ag \
--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.