Bug 1314120 - [RFE] Unify scrub into the client queue
[RFE] Unify scrub into the client queue
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RADOS (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: 2.0
Assigned To: Samuel Just
Bara Ancincova
Depends On:
Blocks: 1322504
  Show dependency treegraph
Reported: 2016-03-02 19:15 EST by Samuel Just
Modified: 2017-07-30 11:10 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Scrub operations are now in the client queue The scrub and trimming operations have been moved to the client operations queue to prioritize client I/O more accurately.
Story Points: ---
Clone Of:
Last Closed: 2016-08-23 15:32:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 8635 None None None 2016-03-02 19:19 EST

  None (edit)
Description Samuel Just 2016-03-02 19:15:26 EST
Description of problem:

Previously, snap trimming and scrub happened in a background thread pool meaning that scrub and snap trimming were scheduled vs client ops at the whim of the os scheduler.  Instead, move them into the same queue with lower priority so that the queue implementation can prioritize client IO directly while avoid starvation.

The main things to test are:
1) scrub throughput is adequate when cluster is not loaded

For this, populate a cluster to let's say 50% full of a mix of rbd and radosgw objects (make sure no single radosgw bucket gets unreasonably large).  Initiate a scrub, make sure the progress is reasonable (doesn't hang, comparable to hammer completion time).  Scrubbing a single pg on a 3 osd cluster is probably adequate.

2) client IO latency doesn't suffer too much (hopefully improves!) compared with hammer during a scrub (deep and shallow)

Populate the cluster as above.  Pick a few precreated rbd images and run fio small writes. Record 99th percentile latency and average throughput while scrubbing (you can probably just set the scrub interval to be very so that they are always scrubbing).  Verify that these do not suffer compared with hammer.
Comment 3 Neil Levine 2016-03-02 19:23:48 EST
Acking this for 2.0 but it needs a conversation with QE to confirm they feel this can be tested.
Comment 12 Ben England 2016-07-19 12:15:51 EDT
not clear if Sam is talking about scrubbing, deep scrubbing or both?  Scrubbing just scans metadata right? which may just be cached for our small disk drives when large RBD objects are used.

Comment 14 errata-xmlrpc 2016-08-23 15:32:59 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.