From: Greg Farnum <gregory.farnum@dreamhost.com>
To: Vladimir Bashkirtsev <vladimir@bashkirtsev.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Possible memory leak in mon?
Date: Wed, 2 May 2012 17:22:17 -0700 [thread overview]
Message-ID: <07C999FE3BF7420ABC05B7CFF88B06AD@dreamhost.com> (raw)
In-Reply-To: <4FA1B50B.8080603@bashkirtsev.com>
On Wednesday, May 2, 2012 at 3:28 PM, Vladimir Bashkirtsev wrote:
> Dear devs,
>
> I have three mons and two of them suddenly consumed around 4G of RAM
> while third one happily lived with 150M. This immediately prompts few
> questions:
>
> 1. What is expected memory use of mon? I believed that mon merely
> directs clients to relevant OSDs and should not consume a lot of
> resources - please correct me if I am wrong.
> 2. In both cases where mon consumed a lot of memory it was preceded by
> disk-full condition and both machines where incidents happened are 64
> bit, rest of cluster 32 bit. mon fs and log files happened to be in the
> same partition - ceph osd produced a lot of messages, filled up disk,
> mon crashed (no core as disk was full), manually deleted logs, restarted
> mon without any issue, some time later found mon using 4G of RAM.
> Running 0.45. Should I deliberately recreate conditions and crash mon to
> get more debug info (if you need it of course, and if yes then what)?
> 3. Does figure 4G per process coming from 32 bit pointers in mon? Or mon
> potentially can consume more than 4G?
>
> Regards,
> Vladimir
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org (mailto:majordomo@vger.kernel.org)
> More majordomo info at http://vger.kernel.org/majordomo-info.html
First: one email is enough.
Second: in normal use your monitors should not consume very much memory. It sounds like something's wrong. Can you please provide the output of "ceph -s"?
Also, do you have any monitor logging on? My best guess is that for some reason the monitors aren't all communicating with each other and so they are buffering messages.
-Greg
next prev parent reply other threads:[~2012-05-03 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 22:28 Possible memory leak in mon? Vladimir Bashkirtsev
2012-05-03 0:22 ` Greg Farnum [this message]
2012-05-03 6:24 ` Vladimir Bashkirtsev
2012-05-03 6:53 ` Greg Farnum
2012-05-07 0:52 ` Vladimir Bashkirtsev
2012-05-07 0:53 ` Vladimir Bashkirtsev
2012-05-14 21:23 ` Gregory Farnum
2012-05-15 17:13 ` Gregory Farnum
2012-05-18 10:07 ` Vladimir Bashkirtsev
2012-05-21 18:18 ` Gregory Farnum
-- strict thread matches above, loose matches on Subject: below --
2012-05-02 22:49 Vladimir Bashkirtsev
2012-05-02 23:36 Vladimir Bashkirtsev
2012-05-02 23:52 Vladimir Bashkirtsev
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=07C999FE3BF7420ABC05B7CFF88B06AD@dreamhost.com \
--to=gregory.farnum@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=vladimir@bashkirtsev.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox