Actions
Bug #37264
closedscrub warning check incorrectly uses mon scrub interval
Status:
Resolved
Priority:
Normal
Assignee:
David Zafman
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
luminous, mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When checking the mon_warn_not_scrubbed the mon_scrub_interval is used instead of osd_scrub_max_interval.
Updated by David Zafman over 5 years ago
The scrub warning also doesn't consider the pool specific scrub interval if specified. The scrub code gets the pool specific interval before falling back to the osd_deep_scrub_interval configuration.
pool.info.opts.get(pool_opts_t::DEEP_SCRUB_INTERVAL, &deep_scrub_interval);
Not sure where in the monitor the pool specific information is stored.
Updated by David Zafman over 5 years ago
- Related to Bug #27988: Warn if queue of scrubs ready to run exceeds some threshold added
Updated by Greg Farnum over 5 years ago
You should be able to get the pool info out of the monitor's OSDMap, if that was a question... :)
Updated by David Zafman over 5 years ago
Updated by David Zafman over 5 years ago
- Status changed from 17 to Pending Backport
- Pull request ID set to 25112
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #38243: mimic: scrub warning check incorrectly uses mon scrub interval added
Updated by Nathan Cutler over 5 years ago
- Copied to Backport #38244: luminous: scrub warning check incorrectly uses mon scrub interval added
Updated by David Zafman about 5 years ago
- Status changed from Pending Backport to Resolved
Actions