* Size of monitor data dir
@ 2012-02-15 2:09 Mandell Degerness
2012-02-15 2:20 ` Sage Weil
0 siblings, 1 reply; 3+ messages in thread
From: Mandell Degerness @ 2012-02-15 2:09 UTC (permalink / raw)
To: ceph-devel
How big can the monitor data directory grow? Is there a rule of thumb
that can be used?
-Mandell Degerness
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Size of monitor data dir
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
0 siblings, 1 reply; 3+ messages in thread
From: Sage Weil @ 2012-02-15 2:20 UTC (permalink / raw)
To: Mandell Degerness; +Cc: ceph-devel, wido
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?
sage
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Size of monitor data dir
2012-02-15 2:20 ` Sage Weil
@ 2012-02-15 12:35 ` Wido den Hollander
0 siblings, 0 replies; 3+ messages in thread
From: Wido den Hollander @ 2012-02-15 12:35 UTC (permalink / raw)
To: Sage Weil; +Cc: Mandell Degerness, ceph-devel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-02-15 12:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.