osd: restoring timely collection of PG stats

500 seconds is way too long, e.g. when compared to the 5s
default configuration option for the manager collection of the OSD data.

Fixes tracker issue 53342 note 5 (a specific scenario leading
to 'not all pgs scrubbed')

Fixes: https://tracker.ceph.com/issues/53342 - partial fix
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>

diff --git a/src/common/options/global.yaml.in b/src/common/options/global.yaml.in
index 072f94a9d7967e9b583d4f0e5590b25c2e13aa40..feb9aeb7b5e597938a532cf63a697fd84a3c2a85 100644 (file)
--- a/src/common/options/global.yaml.in
+++ b/src/common/options/global.yaml.in
@@ -2920,8 +2920,8 @@ options:
   level: advanced
   desc: The maximum interval seconds for update pg's reported_epoch,
         benefit for osdmap trim when osdmap not change frequently.
-  default: 500
   with_legacy: true
+  default: 5
 - name: osd_pg_stat_report_interval_max_epochs
   type: int
   level: advanced