From: Joao Eduardo Luis <joao.luis@inktank.com>
To: "Cláudio Martins" <ctpm@ist.utl.pt>
Cc: ceph-devel@vger.kernel.org
Subject: Re: OSD and MON memory usage
Date: Fri, 16 Nov 2012 18:42:18 +0000 [thread overview]
Message-ID: <50A6890A.4050300@inktank.com> (raw)
In-Reply-To: <20121116172401.ef3e5e52.ctpm@ist.utl.pt>
On 11/16/2012 05:24 PM, Cláudio Martins wrote:
> As for the monitor daemon on this cluster (running on a dedicated
> machine), it is currently using 3.2GB of memory, and it got to that
> point again in a matter of minutes after being restarted. Would it be
> good if we tested with the changes from the wip-mon-leaks-fix branch?
The wip-mon-leaks-fix branch had a regression introduced that would
cause your monitors to crash under certain conditions. The patch that
caused it has been identified and will be removed, but the branch still
needs some more testing before we consider it ready to be merged. We are
aiming however towards early next week.
For the time being, I wouldn't advise you to use that branch.
-Joao
--
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:[~2012-11-16 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 17:24 OSD and MON memory usage Cláudio Martins
2012-11-16 18:42 ` Joao Eduardo Luis [this message]
2012-11-19 23:15 ` Gregory Farnum
2012-11-19 23:20 ` Joao Eduardo Luis
2012-11-23 16:46 ` Joao Eduardo Luis
2012-11-27 17:23 ` Cláudio Martins
2012-11-28 21:00 ` Samuel Just
2012-11-28 21:05 ` Cláudio Martins
2012-11-28 21:08 ` Samuel Just
2012-11-28 21:30 ` Cláudio Martins
2012-11-28 23:13 ` Sylvain Munaut
2012-11-28 23:31 ` Cláudio Martins
2012-12-04 19:29 ` Gregory Farnum
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=50A6890A.4050300@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ctpm@ist.utl.pt \
/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.