Project

General

Profile

Actions

Bug #5050

closed

initial scrub timestamp is 0.000000

Added by Mark Nelson almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
David Zafman
Category:
OSD
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When PGs are created, the initial scrub timestamp is 0.000000 where it should be the current time. With the current behavior, a scrub will be immediately performed on cluster creation even though there is no data present. Because utime_t uses unsigned 32 bit integers, it doesn't appear to be possible to stop this initial scrub by setting a high interval value.

With high PG counts it can take a significant amount of time for the cluster to finish the scrubbing process. Given that it is not immediately obvious that a scrub is in progress, this could lead to users seeing lower than expected benchmarks when testing on freshly created clusters.

Actions #1

Updated by Mark Nelson almost 11 years ago

  • Category set to OSD
Actions #2

Updated by David Zafman almost 11 years ago

  • Status changed from New to In Progress
Actions #3

Updated by David Zafman almost 11 years ago

  • Assignee set to David Zafman
Actions #4

Updated by David Zafman almost 11 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF