From: Filippos Giannakos <philipgian@grnet.gr>
To: Mike Dawson <mike.dawson@cloudapt.com>
Cc: Sage Weil <sage@inktank.com>, Kyle Bader <kyle.bader@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
synnefo-devel@googlegroups.com
Subject: Re: RADOS + deep scrubbing performance issues in production environment
Date: Tue, 28 Jan 2014 20:13:25 +0200 [thread overview]
Message-ID: <20140128181325.GD11532@philipgian-mac> (raw)
In-Reply-To: <52E74E96.8070202@cloudapt.com>
On Tue, Jan 28, 2014 at 01:30:46AM -0500, Mike Dawson wrote:
>
> On 1/27/2014 1:45 PM, Sage Weil wrote:
> >There is also
> >
> > ceph osd set noscrub
> >
> >and then later
> >
> > ceph osd unset noscrub
> >
> In my experience scrub isn't nearly as much of a problem as
> deep-scrub. On a IOPS constrained cluster with writes approaching
> the available aggregate spindle performance minus replication
> penalty and possibly co-located osd journal penalty, scrub may run
> without any disruption. But deep-scrub tends to make iowait on the
> spindles get ugly.
>
> To disable/enable deep-scrub use:
>
> ceph osd set nodeep-scrub
> ceph osd unset nodeep-scrub
>
Yes, deep-scrubbing is much worse than scrubbing, but I think fully disabling it
is not a good option. But having days of degraded performance isn't either.
That's why I am bringing up the problem and seeking for a solid solution
regarding the matter.
Kind Regards,
--
Filippos
<philipgian@grnet.gr>
next prev parent reply other threads:[~2014-01-28 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 15:13 RADOS + deep scrubbing performance issues in production environment Filippos Giannakos
2014-01-27 18:10 ` Kyle Bader
2014-01-27 18:45 ` Sage Weil
2014-01-28 6:30 ` Mike Dawson
2014-01-28 18:13 ` Filippos Giannakos [this message]
2014-01-28 18:13 ` Filippos Giannakos
[not found] ` <066498EC-D137-472A-85DB-93751E85C753@yahoo.com>
[not found] ` <066498EC-D137-472A-85DB-93751E85C753-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2014-02-03 13:40 ` Guang
2015-07-10 13:52 ` icq2206241
2014-01-28 18:12 ` Filippos Giannakos
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=20140128181325.GD11532@philipgian-mac \
--to=philipgian@grnet.gr \
--cc=ceph-devel@vger.kernel.org \
--cc=kyle.bader@gmail.com \
--cc=mike.dawson@cloudapt.com \
--cc=sage@inktank.com \
--cc=synnefo-devel@googlegroups.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 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.