On 03/13/2013 02:06 PM, Stefan Priebe - Profihost AG wrote:
Hi Joao,
Am 13.03.2013 14:58, schrieb Joao Eduardo Luis:
I'm expecting to be able to find the time Real Soon Now to put a doc
together with ways, for anyone willing, to provide us further insight on
what's happening. The monitor is supposed to be able to dump a heap
profile (using gperftools) on-the-fly, but I recall having some issues
with that not so long ago, so that's probably one thing to look into asap.
Thanks - that would be great i'm willing ;-)
Cool, good to know. I'll post something to the ml as soon as I have
something worth sharing. Most likely next week. It's unlikely I'll get
around to do it still this week.
In any case, Stefan, do you by chance still have that monitor going?
Sadly not i needed the memory ;-)
Furthermore, assuming you are using a
version prior to v0.58,
Yes current Bobtail 0.56.3
any chance you can run a 'du -chs
/var/lib/ceph/mon/ceph-foo',
No idea what you expect to see but all mon servers consume 180MB of disk
space.
eh, just trying to figure out if said memory consumption is due to some
large map being kept in memory. Given we always write to the store when
maps are updated, and only after that do we load them to memory, I was
hoping to see some incredibly high disk consumption (while the monitor
was running) in order to assert whether the mem consumption would be
tied to some specific map. But given that the store is periodically
trimmed this was a long shot anyway. Still worth a try though ;)
-Joao
[: ~]# du -chs /ceph/mon
180M /ceph/mon
180M total
Greets,
Stefan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
