.Scrub processes can now be disabled during recovery
A new option `osd_scrub_during_recovery` has been added with this release. Setting this option to `false` in the Ceph configuration file disables starting new scrub processes during recovery. As a result, the speed of the recovery is enhanced.
Description of problem:Manually suspending scrubs and deep-scubs seems to improve backfill, recovery, rebalancing seems to enhance speed and reduce the number of slow requests logged. A method to make this the default behavior is desirable to customers that suffer poor performance during these operations is requested.
Version-Release number of selected component (if applicable):Firefly
How reproducible:Consistent behavior
Steps to Reproduce:
1.Add, remove OSDs during scrub operations.
This is a committed Tufnell feature.
Thanks. What's the timeline for Tufnell? T seems a long ways down the alphabet, does the change from the cephalopod naming scheme to Spinal Tap skip a bunch of letters?
The Cephalopod names refer to the upstream, community releases which downstream is based.
Tufnell is the codename for Red Hat Ceph Storage v2.0 - ie the downstream product. This will likely be based on Ceph v10 (Jewel) due out later this year. Tufnell is likely to arrive shortly after in Q1 2016.
Ah, gotcha, thanks. Had heard something about community and RCS forking but had not known of the naming roadmap.
I’m proposing to add this BZ to the 2.3 release notes. If you agree, could you set the “Doc Type” and “Doc Text” fields?
When Recovery/backfill operation starts, will the scrubbing be suspended for scheduled scrub or manual scrub(will manual scrub override it?) or both?
discussed at program meeting, nobody is clear what should happen to this bug for 2.3 ... Neil to discuss with engineering and figure out next steps
As per the clarification given I ran following steps:
1. Started long recovery and ran scrub/deep scrub on several osds
2. Monitored cluster status and "ceph pg dump", found no PGs both recovering and scrubbing.
This has now been verified so I believe that any issues from me have been resolved.
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.