Actions
Feature #5041
openDeep scrub CPU limit behavior
Status:
New
Priority:
Normal
Assignee:
-
Category:
OSD
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Determine if deep scrub is properly using the CPU utilization limits (rather than just scrub). If not, should it? More generally, should we be using CPU utilization at all or migrate to something like client initiated operations or data throughput as metrics?
No data to display
Actions