New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
osd: Add config option to skip running the osd benchmark during init and update documentation. #42604
Conversation
3997403
to
00f6d0b
Compare
fbedee8
to
11881c6
Compare
11881c6
to
693e93b
Compare
Per @sseshasa this requires some changes |
Introduce a new dev config option "osd_mclock_skip_benchmark" that when set skips running the OSD benchmark on start-up. By default this option is disabled. This is useful in the following scenarios: - Dev/CI testing, - Configurations that don't need QoS. If the option is enabled, the default OSD iops capacity is read from osd_mclock_max_capacity_iops_[hdd,ssd]. Fixes: https://tracker.ceph.com/issues/52025 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com>
…city. Update the steps in the mclock config reference document to manually override an OSDs max IOPS capacity. Provide information on the alternative ways to override the osd_mclock_max_capacity_iops_[hdd,ssd] options for an OSD. Fixes: https://tracker.ceph.com/issues/52025 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com>
…ark option Add a standalone test - test_activate_osd_skip_benchmark() in ceph-helpers.sh that exercises the osd-mclock-skip-benchmark option. Fixes: https://tracker.ceph.com/issues/52025 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com>
4f6a252
to
266b1ae
Compare
Force a subset of tests that explicitly employ the filestore backend to use WPQ scheduler. This is because mclock scheduler will not be optimized for filestore. Fixes: https://tracker.ceph.com/issues/52025 Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com>
266b1ae
to
7dcede7
Compare
@neha-ojha I had made changes to qa/objectstore/filestore-xfs.yaml and qa/objectstore_debug/filestore-xfs.yaml to use 'wpq'. But when teuthology runs the tests, the settings for 'osd op queue' in the above files are overridden by the settings in rados.yaml that is applied subsequently thus making the changes redundant. For e.g. see the tests in the run http://pulpito.front.sepia.ceph.com/sseshasa-2021-09-02_07:53:45-rados-wip-sseshasa2-testing-2021-09-01-1728-distro-basic-smithi/. One such test is shown below:
The overrides in rados.yaml are applied after the filestore-xfs overrides (where I made the changes to use 'wpq') are applied and therefore made redundant. But the tests do pass with mclock scheduler and therefore I am removing it from this PR. Unless there's a way to prevent/avoid the override, this PR can be merged since there were no related failures in Yuri's run. I can update this PR with details of that run if this can be merged. |
We'll probably need to restructure the facets to make filestore-xfs overrides take precedence, but I don't think it is required if the tests are passing. Let's go ahead and update rados run details and merge this PR. |
Teuthology Testing Result: Failures (Unrelated):
|
Introduce a new dev config option "osd_mclock_skip_benchmark" that when
set skips running the OSD benchmark on start-up. By default this option is
disabled. This is useful in the following scenarios:
Update mclock-config-ref doc steps to override osd max iops capacity.
Fixes: https://tracker.ceph.com/issues/52025
Signed-off-by: Sridhar Seshasayee sseshasa@redhat.com
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox