From 8537dff175b25e2f0e20aa252bee6fa79def2a33 Mon Sep 17 00:00:00 2001 From: Neha Ojha Date: Mon, 3 May 2021 18:35:35 +0000 Subject: [PATCH] common/options/global.yaml.in: use mclock_scheduler as the default scheduler The aim is to default to mclock_scheduler in quincy, so start early and get more testing. Signed-off-by: Neha Ojha --- src/common/options/global.yaml.in | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/common/options/global.yaml.in b/src/common/options/global.yaml.in index a6a7da1311f0f..74775b0ab7b56 100644 --- a/src/common/options/global.yaml.in +++ b/src/common/options/global.yaml.in @@ -4450,19 +4450,18 @@ options: type: str level: advanced desc: which operation priority queue algorithm to use - long_desc: which operation priority queue algorithm to use; mclock_scheduler is - currently experimental + long_desc: which operation priority queue algorithm to use fmt_desc: This sets the type of queue to be used for prioritizing ops within each OSD. Both queues feature a strict sub-queue which is dequeued before the normal queue. The normal queue is different between implementations. The WeightedPriorityQueue (``wpq``) dequeues operations in relation to their priorities to prevent starvation of any queue. WPQ should help in cases where a few OSDs - are more overloaded than others. The new mClockQueue + are more overloaded than others. The mClockQueue (``mclock_scheduler``) prioritizes operations based on which class they belong to (recovery, scrub, snaptrim, client op, osd subop). See `QoS Based on mClock`_. Requires a restart. - default: wpq + default: mclock_scheduler see_also: - osd_op_queue_cut_off enum_values: -- 2.39.5