From: Wido den Hollander <wido@widodh.nl>
To: Sage Weil <sage@newdream.net>
Cc: Mandell Degerness <mandell@pistoncloud.com>, ceph-devel@vger.kernel.org
Subject: Re: Size of monitor data dir
Date: Wed, 15 Feb 2012 13:35:59 +0100 [thread overview]
Message-ID: <4F3BA6AF.1080308@widodh.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.1202141818560.3836@cobra.newdream.net>
On 02/15/2012 03:20 AM, Sage Weil wrote:
> On Tue, 14 Feb 2012, Mandell Degerness wrote:
>> How big can the monitor data directory grow? Is there a rule of thumb
>> that can be used?
>
> Right now the monitor dir include teh cluster log files (log and log.*),
> which grow indefinitely unless you rotate them. The other directories
> are mostly trimmed by the monitor itself and should stay pretty small (few
> hundred megs at most?). The lingering exception is the mdsmap dir, which
> isn't yet trimmed, but you guys won't be using that anyway (and the maps
> are small).
>
> Maybe Wido or someone else who has a long running cluster can see how big
> it is?
I just took a look at my oldest cluster, which has been running for
about 4 months now with a single monitor.
This cluster has 6 OSD's and is running two virtual machines with RBD.
The monitor directory is 29M right now.
On my larger cluster, which I had to re-install, the monitor directories
are about 400M.
The logm directory is however trimmed? My oldest messages are from
February 14th on both clusters.
I'd however advice somewhere around 5GB at at least. I'm running my
monitors on ext4 and I've ran out of inodes a couple of times. But if
all directories are trimmed, you are not likely to run into that.
You should however be careful with the log.* files, they can grow
quickly. We could provide a standard logrotate script in the deb's /
rpm's for those?
Wido
prev parent reply other threads:[~2012-02-15 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 2:09 Size of monitor data dir Mandell Degerness
2012-02-15 2:20 ` Sage Weil
2012-02-15 12:35 ` Wido den Hollander [this message]
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=4F3BA6AF.1080308@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=mandell@pistoncloud.com \
--cc=sage@newdream.net \
/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.