From 97043a8c134c69fd5a3e0cb41dfda5526c3ad917 Mon Sep 17 00:00:00 2001 From: Sridhar Seshasayee Date: Tue, 5 Apr 2022 21:15:24 +0530 Subject: [PATCH] PendingReleaseNotes: Update mclock release note regarding an existing issue Signed-off-by: Sridhar Seshasayee --- PendingReleaseNotes | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/PendingReleaseNotes b/PendingReleaseNotes index 10bd8ce5b5b3b..ee7ec9145318f 100644 --- a/PendingReleaseNotes +++ b/PendingReleaseNotes @@ -64,14 +64,21 @@ * RGW: `radosgw-admin realm delete` is now renamed to `radosgw-admin realm rm`. This is consistent with the help message. -* OSD: Ceph now uses mclock_scheduler for bluestore OSDs as its default osd_op_queue +* OSD: Ceph now uses mclock_scheduler for BlueStore OSDs as its default osd_op_queue to provide QoS. The 'mclock_scheduler' is not supported for filestore OSDs. - Therefore, the default 'osd_op_queue' is set to 'wpq' for filestore OSDs + Therefore, the default 'osd_op_queue' is set to 'wpq' for Filestore OSDs and is enforced even if the user attempts to change it. For more details on configuring mclock see, https://docs.ceph.com/en/latest/rados/configuration/mclock-config-ref/ + An outstanding issue exists during runtime where the mclock config options + related to reservation, weight and limit cannot be modified after switching + to the 'custom' mclock profile using the "ceph config set ..." command. + This is tracked by: https://tracker.ceph.com/issues/55153. Until the issue is + fixed, users are advised to avoid using the 'custom' profile or use the + workaround mentioned in the tracker. + * CephFS: Failure to replay the journal by a standby-replay daemon will now cause the rank to be marked damaged. -- 2.39.5