From: Mike Dawson <mike.dawson-9dgm/EUDD3RBYT3KYJiKsA@public.gmane.org>
To: Sylvain Munaut
<s.munaut-IEbV4ISQ1OTUSxYbhEqsfVaTQe2KTcn/@public.gmane.org>
Cc: ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org,
"ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: mon IO usage
Date: Tue, 21 May 2013 09:25:06 -0400 [thread overview]
Message-ID: <519B75B2.4070405@scholarstack.com> (raw)
In-Reply-To: <519B6F28.9000400-9dgm/EUDD3RBYT3KYJiKsA@public.gmane.org>
Thanks for the correction on IRC. I should have written that this issue
started with 0.59 (when the monitor changes hit).
http://ceph.com/dev-notes/cephs-new-monitor-changes/
The writeup and release notes sometimes say they went in for 0.58, but I
believe they were actually released in 0.59.
Thanks for the correction Sylvain.
- Mike
On 5/21/2013 8:57 AM, Mike Dawson wrote:
> Sylvain,
>
> I can confirm I see a similar traffic pattern.
>
> Any time I have lots of writes going to my cluster (like heavy writes
> from RBD or remapping/backfilling after losing an OSD), I see all sorts
> of monitor issues.
>
> If my monitor leveldb store.db directories grow past some unknown point
> (maybe ~1GB or so), 'compact on trim' is insufficiently slow. The
> store.db grows faster than compact can trim the garbage. After that
> point, the only hope to rein in the store.db size is to stop the OSDs
> and get leveldb to compact without any ongoing writes.
>
> I sent Sage and Joao a transaction dump of the growth yesterday. Sage
> looked, but the files are so large it is tough to get useful info.
>
> http://tracker.ceph.com/issues/4895
>
> I believe this issue has existed since 0.48.
>
> - Mike
>
> On 5/21/2013 8:16 AM, Sylvain Munaut wrote:
>> Hi,
>>
>>
>> I've just added some monitoring to the IO usage of mon (trying to
>> track down that growing mon issue), and I'm kind of surprised by the
>> amount of IO generated by the monitor process.
>>
>> I get continuous 4 Mo/s / 75 iops with added big spikes at each
>> compaction every 3 min or so.
>>
>> Is there a description somewhere of what the monitor does exactly ? I
>> mean the monmap / pgmap / osdmap / mdsmap / election epoch don't
>> change that often (pgmap is like 1 per second and that's the fastest
>> change by several orders of magnitude). So what exactly does the
>> monitor do with all that IO ???
>>
>>
>> Cheers,
>>
>> Sylvain
>> _______________________________________________
>> ceph-users mailing list
>> ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>
next prev parent reply other threads:[~2013-05-21 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF6-1L4oWCwNxywALb=cUNP_pbD=ND631MJqvCWyvAfvNdWauQ@mail.gmail.com>
2013-05-21 12:57 ` [ceph-users] mon IO usage Mike Dawson
[not found] ` <519B6F28.9000400-9dgm/EUDD3RBYT3KYJiKsA@public.gmane.org>
2013-05-21 13:25 ` Mike Dawson [this message]
2013-05-21 15:52 ` Sylvain Munaut
2013-05-21 15:56 ` Gregory Farnum
2013-05-21 15:57 ` Sage Weil
2013-05-21 16:05 ` Sylvain Munaut
[not found] ` <CAF6-1L4C1QQHZ_5=3OCATFTCD_As63HEjJLcKsGURAV02PFQPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-21 16:10 ` Sage Weil
2013-05-21 18:51 ` [ceph-users] " Sylvain Munaut
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=519B75B2.4070405@scholarstack.com \
--to=mike.dawson-9dgm/eudd3rbyt3kyjiksa@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org \
--cc=s.munaut-IEbV4ISQ1OTUSxYbhEqsfVaTQe2KTcn/@public.gmane.org \
/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.