All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Bashkirtsev <vladimir@bashkirtsev.com>
To: Greg Farnum <gregory.farnum@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Possible memory leak in mon?
Date: Mon, 07 May 2012 10:22:02 +0930	[thread overview]
Message-ID: <4FA71CB2.7070902@bashkirtsev.com> (raw)
In-Reply-To: <A1BA6F85E3224387AFB0C24A7786B470@dreamhost.com>

On 03/05/12 16:23, Greg Farnum wrote:
> On Wednesday, May 2, 2012 at 11:24 PM, Vladimir Bashkirtsev wrote:
>> Greg,
>>
>> Apologies for multiple emails: my mail server is backed by ceph now and
>> it struggled this morning (separate issue). So my mail server reported
>> back to my mailer that sending of email failed when obviously it was not
>> the case.
> Interesting — I presume you're using the file system? That's not something we've heard of anybody doing with Ceph before. :)
>
>>
>> [root@gamma ~]# ceph -s
>> 2012-05-03 15:46:55.640951 mds e2666: 1/1/1 up {0=1=up:active}, 1
>> up:standby
>> 2012-05-03 15:46:55.647106 osd e10728: 6 osds: 6 up, 6 in
>> 2012-05-03 15:46:55.654052 log 2012-05-03 15:46:26.557084 mon.2
>> 172.16.64.202:6789/0 2878 : [INF] mon.2 calling new monitor election
>> 2012-05-03 15:46:55.654425 mon e7: 3 mons at
>> {0=172.16.64.200:6789/0,1=172.16.64.201:6789/0,2=172.16.64.202:6789/0}
>> 2012-05-03 15:46:56.961624 pg v1251669: 600 pgs: 2 creating, 598
>> active+clean; 309 GB data, 963 GB used, 1098 GB / 2145 GB avail
>>
>> Loggin is on but nothing obvious in there: logs quite small. Number of
>> ceph health logged (ceph monitored by nagios and so this record appears
>> every 5 minutes), monitors periodically call for election (different
>> periods between 1 to 15 minutes as it looks). That's it.
> Hrm. Generally speaking the monitors shouldn't call for elections unless something changes (one of them crashes) or the leader monitor is slowing down.
> Can you increase the debug_mon to 20, the debug_ms to 1, and post one of the logs somewhere? The "Live Debugging" section of http://ceph.com/wiki/Debugging should give you what you need. :)
Here's the logs and core dumps:
http://www.bashkirtsev.com/logs-2012-05-07.tar.bz2

Mons grown to 1.2GB and 2GB of memory.
>
>>
>> Regards,
>> Vladimir
>

--
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

  reply	other threads:[~2012-05-07  0:52 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
2012-05-03  6:24   ` Vladimir Bashkirtsev
2012-05-03  6:53     ` Greg Farnum
2012-05-07  0:52       ` Vladimir Bashkirtsev [this message]
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=4FA71CB2.7070902@bashkirtsev.com \
    --to=vladimir@bashkirtsev.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gregory.farnum@dreamhost.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.