Actions
Fix #51464
closedosd: Add mechanism to avoid running osd benchmark on osd init when using mclock_scheduler.
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
-
% Done:
100%
Source:
Development
Tags:
Backport:
pacific
Reviewed:
Affected Versions:
Description
The current behavior is to let the osd benchmark run on each osd
init, which is not necessary. If the underlying device for an osd
is a HDD, then the osd initialization time is increased
significantly and which could have undesirable side-effects.
Therefore, a mechanism to avoid running the benchmark on every init
is necessary. Also, it would also be helpful to have a way to force
a benchmark run on an osd init.
Updated by Sridhar Seshasayee almost 3 years ago
- Category changed from Correctness/Safety to Administration/Usability
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 42133
Updated by Sridhar Seshasayee almost 3 years ago
- Subject changed from osd: Add mechanism to avoid running osd benchmark on osd init. to osd: Add mechanism to avoid running osd benchmark on osd init when using mclock_scheduler.
Updated by Sridhar Seshasayee almost 3 years ago
- Related to Backport #51117: pacific: osd: Run osd bench test to override default max osd capacity for mclock. added
Updated by Sridhar Seshasayee almost 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to pacific
Updated by Backport Bot almost 3 years ago
- Copied to Backport #51988: pacific: osd: Add mechanism to avoid running osd benchmark on osd init when using mclock_scheduler. added
Updated by Sridhar Seshasayee over 2 years ago
- Status changed from Pending Backport to Resolved
Actions