Project

General

Profile

Actions

Feature #11387

closed

osd: get more reasonable scrub_reg_stamp

Added by Xinze Chi about 9 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

If we execute the command "ceph osd set nodeep-scrub", the last_scrub_stamp
would be osd_deep_scrub_interval largger than last_deep_scrub. E.g.,

pg_stat last_scrub scrub_stamp last_deep_scrub deep_scrub_stamp
2.d8 35845'2779955 2015-04-10 16:49:32.340098 35666'2695089 2015-04-01 21:39:13.234161

And then, If we set nodeep-scrub sometime of the day, case below would be possible.

PG scrub_stamp deep_scrub_stamp
A 8 2
B 9 1

If the osd_deep_scrub_interval is 7 and osd_scrub_min_interval is 1. I think we should
schedule PG B first instead of PG A, because PG B is time for deep scrub.

Actions #1

Updated by David Zafman about 9 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF