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
quincy: osd: Change scrub cost in case of mClock scheduler #51728
quincy: osd: Change scrub cost in case of mClock scheduler #51728
Conversation
3290cc7
to
dfdfcb9
Compare
|
Changes look good. Some minor nits related to backport requirements need addressing:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM apart from the minor nits about the backport PRs and commit message.
Thanks @sseshasa I'll update the commit message. |
With osd_op_queue as WPQ, high costs were assigned to scrub in order to throttle it effectively. In the case of mClock scheduler, mClock parameters are used to do the throttling and the cost should represent a realistic value. Fixes: https://tracker.ceph.com/issues/61313 Signed-off-by: Aishwarya Mathuria <amathuri@redhat.com> (cherry picked from commit 43544d2) src/osd/OSD.cc: We are using osd_scrub_chunk_max in the scrub cost calculation here.
All the mClock profiles enforce no minimum reservation for the background best-effort client. For this purpose, the default_min value should 0 and not 1. Signed-off-by: Aishwarya Mathuria <amathuri@redhat.com> (cherry picked from commit 05848b4)
5c8b208
to
85c39a0
Compare
|
jenkins test make check |
2 similar comments
|
jenkins test make check |
|
jenkins test make check |
With osd_op_queue as WPQ, high costs were assigned to scrub in order to throttle it effectively. In the case of mClock scheduler, mClock parameters are used to do the throttling and the cost should represent a realistic value.
Fixes: https://tracker.ceph.com/issues/61313
Signed-off-by: Aishwarya Mathuria amathuri@redhat.com
(cherry picked from commit 43544d2)
Backport of #51656
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows