osd/scrub: decrease default deep scrub chunk size

The previous default of 25 objects per chunk proved to take too long
(many hundreds of milliseconds) on a busy cluster. As the scrubber
locks all objects in the chunk for the duration, a large chunk size
can cause a significant impact on the client ops' latencies.

Fixes: https://tracker.ceph.com/issues/68057
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>
(cherry picked from commit 8c2ed94e9cbc7b1ed84b034a65b126e16b18a596)

diff --git a/src/common/options/osd.yaml.in b/src/common/options/osd.yaml.in
index a9596cec1d790a07bc9b1f8de401c3c14efc691c..379b526a218026953c0840fe4557d104d0bb14e4 100644 (file)
--- a/src/common/options/osd.yaml.in
+++ b/src/common/options/osd.yaml.in
@@ -344,8 +344,10 @@ options:
   type: int
   level: advanced
   desc: Maximum number of objects to deep-scrub in a single chunk
-  fmt_desc: The maximum number of object store chunks to scrub during single operation.
-  default: 25
+  fmt_desc: The maximum number of objects to deep-scrub during single internal
+    scrub operation. Large values would improve scrubbing performance but
+    may adversely affect client operations latency.
+  default: 15
   see_also:
   - osd_scrub_chunk_min
   with_legacy: true