From: Stefan Priebe <s.priebe@profihost.ag>
To: Wido den Hollander <wido@42on.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Higher OSD disk util due to RBD snapshots from Dumpling to Firefly
Date: Thu, 01 Jan 2015 10:30:45 +0100 [thread overview]
Message-ID: <54A513C5.6040407@profihost.ag> (raw)
In-Reply-To: <54A42280.60607@42on.com>
hi,
Am 31.12.2014 um 17:21 schrieb Wido den Hollander:
> Hi,
>
> Last week I upgraded a 250 OSD cluster from Dumpling 0.67.10 to Firefly
> 0.80.7 and after the upgrade there was a severe performance drop on the
> cluster.
>
> It started raining slow requests after the upgrade and most of them
> included a 'snapc' in the request.
>
> That lead me to investigate the RBD snapshots and I found that a rogue
> process had created ~1800 snapshots spread out over 200 volumes.
>
> One image even had 181 snapshots!
>
> As the snapshots weren't used I removed them all and after the snapshots
> were removed the performance of the cluster came back to normal level again.
>
> I'm wondering what changed between Dumpling and Firefly which caused
> this? I saw OSDs spiking to 100% disk util constantly under Firefly
> where this didn't happen with Dumpling.
>
> Did something change in the way OSDs handle RBD snapshots which causes
> them to create more disk I/O?
I saw the same and addionally a slowdown in librbd too, that's why i'm
still on dumpling and won't upgrade until hammer.
Stefan
next prev parent reply other threads:[~2015-01-01 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 16:21 Higher OSD disk util due to RBD snapshots from Dumpling to Firefly Wido den Hollander
2015-01-01 9:30 ` Stefan Priebe [this message]
2015-01-02 16:49 ` Samuel Just
2015-01-02 18:43 ` Stefan Priebe
2015-01-02 19:02 ` Samuel Just
2015-01-07 16:51 ` Dan van der Ster
2015-01-08 7:55 ` Wido den Hollander
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=54A513C5.6040407@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=wido@42on.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox