Bug 2208600 - Update the mClock documentation to reflect the new mclock profile information and other important changes.
Summary: Update the mClock documentation to reflect the new mclock profile information...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 6.1
Assignee: Akash Raj
QA Contact: skanta
Rivka Pollack
URL:
Whiteboard:
Depends On:
Blocks: 2192813
TreeView+ depends on / blocked
 
Reported: 2023-05-19 17:28 UTC by Sridhar Seshasayee
Modified: 2023-06-21 06:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Usability and design improvements are implemented to the mClock scheduler With this release, significant usability and design improvements are implemented to the mClock scheduler to address the slow backfill issues. - The `balanced` profile is set as the default mClock profile because it represents a compromise between prioritizing client IO or recovery IO. Users can then choose either the `high_client_ops` profile to prioritize client IO or the `high_recovery_ops` profile to prioritize recovery IO. - QoS parameters like _reservation_ and _limit_ are now specified in terms of a fraction (`range`: `0.0` to `1.0`) of the OSD's IOPS capacity. - The cost parameters - `osd_mclock_cost_per_io_usec_*` and `osd_mclock_cost_per_byte_usec_*` have been removed. The cost of an operation is now determined using the random IOPS and maximum sequential bandwidth capability of the OSD's underlying device. - Degraded object recovery is given higher priority when compared to misplaced object recovery because degraded objects present a data safety issue not present with objects that are merely misplaced. Therefore, backfilling operations with the `balanced` and `high_client_ops` mClock profiles may progress slower than what was seen with the `WeightedPriorityQueue` (WPQ) scheduler. - The QoS allocations in all the mClock profiles are optimized based on the above fixes and enhancements.
Clone Of:
Environment:
Last Closed: 2023-06-21 06:59:51 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6703 0 None None None 2023-05-19 17:29:39 UTC

Description Sridhar Seshasayee 2023-05-19 17:28:10 UTC 
Describe the issue:

With the recent changes to mClock scheduler and recovery specific changes to address
the slow backfill issue (see https://bugzilla.redhat.com/show_bug.cgi?id=2163473),
the following significant changes were introduced:

1. Change the way QoS parameters are specified in mclock profiles.
2. The allocations for different ops within profiles are changed
3. The default mclock profile is now changed.
4. The earlier cost related config parameters are removed and new ones are
   introduced.
5. The recovery and backfill limits are changed.
6. Miscellaneous changes to a few subsections.

All the above changes are already present in the upstream documentation, the link
for which is mentioned below under the "Document URL" section.


Document URL:
https://docs.ceph.com/en/quincy/rados/configuration/mclock-config-ref/

Additional information:
The upstream documentation can be used as reference to modify the affected sections in the downstream documentation. I can provide additional inputs when necessary.
Comment 1 RHEL Program Management 2023-05-19 17:28:22 UTC 
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
Comment 10 Manisha Saini 2023-06-05 18:55:30 UTC 
Thanks Akash for fixing this.

Clearing the needinfo on my name as Sridhar will be verifying this BZ
Note You need to log in before you can comment on or make changes to this bug.