Operations
==========
- ``osd_op_queue``
-
-:Description: 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
- (``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.
-
-:Type: String
-:Valid Choices: wpq, mclock_scheduler
-:Default: ``wpq``
-
-
-``osd_op_queue_cut_off``
-
-:Description: This selects which priority ops will be sent to the strict
- queue verses the normal queue. The ``low`` setting sends all
- replication ops and higher to the strict queue, while the ``high``
- option sends only replication acknowledgment ops and higher to
- the strict queue. Setting this to ``high`` should help when a few
- OSDs in the cluster are very busy especially when combined with
- ``wpq`` in the ``osd_op_queue`` setting. OSDs that are very busy
- handling replication traffic could starve primary client traffic
- on these OSDs without these settings. Requires a restart.
-
-:Type: String
-:Valid Choices: low, high
-:Default: ``high``
-
-
-``osd_client_op_priority``
-
-:Description: The priority set for client operations. This value is relative
- to that of ``osd_recovery_op_priority`` below. The default
- strongly favors client ops over recovery.
-
-:Type: 32-bit Integer
-:Default: ``63``
-:Valid Range: 1-63
-
-
-``osd_recovery_op_priority``
-
-:Description: The priority of recovery operations vs client operations, if not specified by the
- pool's ``recovery_op_priority``. The default value prioritizes client
- ops (see above) over recovery ops. You may adjust the tradeoff of client
- impact against the time to restore cluster health by lowering this value
- for increased prioritization of client ops, or by increasing it to favor
- recovery.
-
-:Type: 32-bit Integer
-:Default: ``3``
-:Valid Range: 1-63
-
-
-``osd_scrub_priority``
-
-:Description: The default work queue priority for scheduled scrubs when the
- pool doesn't specify a value of ``scrub_priority``. This can be
- boosted to the value of ``osd_client_op_priority`` when scrubs are
- blocking client operations.
-
-:Type: 32-bit Integer
-:Default: ``5``
-:Valid Range: 1-63
-
-
-``osd_requested_scrub_priority``
-
-:Description: The priority set for user requested scrub on the work queue. If
- this value were to be smaller than ``osd_client_op_priority`` it
- can be boosted to the value of ``osd_client_op_priority`` when
- scrub is blocking client operations.
-
-:Type: 32-bit Integer
-:Default: ``120``
-
-
-``osd_snap_trim_priority``
-
-:Description: The priority set for the snap trim work queue.
-
-:Type: 32-bit Integer
-:Default: ``5``
-:Valid Range: 1-63
-
-``osd_snap_trim_sleep``
-
-:Description: Time in seconds to sleep before next snap trim op.
- Increasing this value will slow down snap trimming.
- This option overrides backend specific variants.
-
-:Type: Float
-:Default: ``0``
-
-
-``osd_snap_trim_sleep_hdd``
-
-:Description: Time in seconds to sleep before next snap trim op
- for HDDs.
-
-:Type: Float
-:Default: ``5``
-
-
-``osd_snap_trim_sleep_ssd``
-
-:Description: Time in seconds to sleep before next snap trim op
- for SSD OSDs (including NVMe).
-
-:Type: Float
-:Default: ``0``
-
-
-``osd_snap_trim_sleep_hybrid``
-
-:Description: Time in seconds to sleep before next snap trim op
- when OSD data is on an HDD and the OSD journal or WAL+DB is on an SSD.
-
-:Type: Float
-:Default: ``2``
-
-``osd_op_thread_timeout``
-
-:Description: The Ceph OSD Daemon operation thread timeout in seconds.
-:Type: 32-bit Integer
-:Default: ``15``
-
-
-``osd_op_complaint_time``
-
-:Description: An operation becomes complaint worthy after the specified number
- of seconds have elapsed.
-
-:Type: Float
-:Default: ``30``
-
-
-``osd_op_history_size``
-
-:Description: The maximum number of completed operations to track.
-:Type: 32-bit Unsigned Integer
-:Default: ``20``
-
-
-``osd_op_history_duration``
-
-:Description: The oldest completed operation to track.
-:Type: 32-bit Unsigned Integer
-:Default: ``600``
-
-
-``osd_op_log_threshold``
-
-:Description: How many operations logs to display at once.
-:Type: 32-bit Integer
-:Default: ``5``
-
+.. confval:: osd_op_queue
+.. confval:: osd_op_queue_cut_off
+.. confval:: osd_client_op_priority
+.. confval:: osd_recovery_op_priority
+.. confval:: osd_scrub_priority
+.. confval:: osd_requested_scrub_priority
+.. confval:: osd_snap_trim_priority
+.. confval:: osd_snap_trim_sleep
+.. confval:: osd_snap_trim_sleep_hdd
+.. confval:: osd_snap_trim_sleep_ssd
+.. confval:: osd_snap_trim_sleep_hybrid
+.. confval:: osd_op_thread_timeout
+.. confval:: osd_op_complaint_time
+.. confval:: osd_op_history_size
+.. confval:: osd_op_history_duration
+.. confval:: osd_op_log_threshold
.. _dmclock-qos:
mClock and dmClock experiments on the ``ceph-devel`` mailing list.
-``osd_push_per_object_cost``
-
-:Description: the overhead for serving a push op
-
-:Type: Unsigned Integer
-:Default: 1000
-
-
-``osd_recovery_max_chunk``
-
-:Description: the maximum total size of data chunks a recovery op can carry.
-
-:Type: Unsigned Integer
-:Default: 8 MiB
-
-
-``osd_mclock_scheduler_client_res``
-
-:Description: IO proportion reserved for each client (default).
-
-:Type: Unsigned Integer
-:Default: 1
-
-
-``osd_mclock_scheduler_client_wgt``
-
-:Description: IO share for each client (default) over reservation.
-
-:Type: Unsigned Integer
-:Default: 1
-
-
-``osd_mclock_scheduler_client_lim``
-
-:Description: IO limit for each client (default) over reservation.
-
-:Type: Unsigned Integer
-:Default: 999999
-
-
-``osd_mclock_scheduler_background_recovery_res``
-
-:Description: IO proportion reserved for background recovery (default).
-
-:Type: Unsigned Integer
-:Default: 1
-
-
-``osd_mclock_scheduler_background_recovery_wgt``
-
-:Description: IO share for each background recovery over reservation.
-
-:Type: Unsigned Integer
-:Default: 1
-
-
-``osd_mclock_scheduler_background_recovery_lim``
-
-:Description: IO limit for background recovery over reservation.
-
-:Type: Unsigned Integer
-:Default: 999999
-
-
-``osd_mclock_scheduler_background_best_effort_res``
-
-:Description: IO proportion reserved for background best_effort (default).
-
-:Type: Unsigned Integer
-:Default: 1
-
-
-``osd_mclock_scheduler_background_best_effort_wgt``
-
-:Description: IO share for each background best_effort over reservation.
-
-:Type: Unsigned Integer
-:Default: 1
-
-
-``osd_mclock_scheduler_background_best_effort_lim``
-
-:Description: IO limit for background best_effort over reservation.
-
-:Type: Unsigned Integer
-:Default: 999999
+.. confval:: osd_push_per_object_cost
+.. confval:: osd_mclock_scheduler_client_res
+.. confval:: osd_mclock_scheduler_client_wgt
+.. confval:: osd_mclock_scheduler_client_lim
+.. confval:: osd_mclock_scheduler_background_recovery_res
+.. confval:: osd_mclock_scheduler_background_recovery_wgt
+.. confval:: osd_mclock_scheduler_background_recovery_lim
+.. confval:: osd_mclock_scheduler_background_best_effort_res
+.. confval:: osd_mclock_scheduler_background_best_effort_wgt
+.. confval:: osd_mclock_scheduler_background_best_effort_lim
.. _the dmClock algorithm: https://www.usenix.org/legacy/event/osdi10/tech/full_papers/Gulati.pdf
-
.. index:: OSD; backfilling
Backfilling
priority than requests to read or write data.
-``osd_max_backfills``
-
-:Description: The maximum number of backfills allowed to or from a single OSD.
- Note that this is applied separately for read and write operations.
-:Type: 64-bit Unsigned Integer
-:Default: ``1``
-
-
-``osd_backfill_scan_min``
-
-:Description: The minimum number of objects per backfill scan.
-
-:Type: 32-bit Integer
-:Default: ``64``
-
-
-``osd_backfill_scan_max``
-
-:Description: The maximum number of objects per backfill scan.
-
-:Type: 32-bit Integer
-:Default: ``512``
-
-
-``osd_backfill_retry_interval``
-
-:Description: The number of seconds to wait before retrying backfill requests.
-:Type: Double
-:Default: ``10.0``
+.. confval:: osd_max_backfills
+.. confval:: osd_backfill_scan_min
+.. confval:: osd_backfill_scan_max
+.. confval:: osd_backfill_retry_interval
.. index:: OSD; osdmap
number of map epochs increases. Ceph provides some settings to ensure that
Ceph performs well as the OSD map grows larger.
-
-``osd_map_dedup``
-
-:Description: Enable removing duplicates in the OSD map.
-:Type: Boolean
-:Default: ``true``
-
-
-``osd_map_cache_size``
-
-:Description: The number of OSD maps to keep cached.
-:Type: 32-bit Integer
-:Default: ``50``
-
-
-``osd_map_message_max``
-
-:Description: The maximum map entries allowed per MOSDMap message.
-:Type: 32-bit Integer
-:Default: ``40``
-
-
+.. confval:: osd_map_dedup
+.. confval:: osd_map_cache_size
+.. confval:: osd_map_message_max
.. index:: OSD; recovery
the number recovery requests, threads and object chunk sizes which allows Ceph
perform well in a degraded state.
-
-``osd_recovery_delay_start``
-
-:Description: After peering completes, Ceph will delay for the specified number
- of seconds before starting to recover RADOS objects.
-
-:Type: Float
-:Default: ``0``
-
-
-``osd_recovery_max_active``
-
-:Description: The number of active recovery requests per OSD at one time. More
- requests will accelerate recovery, but the requests places an
- increased load on the cluster.
-
- This value is only used if it is non-zero. Normally it
- is ``0``, which means that the ``hdd`` or ``ssd`` values
- (below) are used, depending on the type of the primary
- device backing the OSD.
-
-:Type: 32-bit Integer
-:Default: ``0``
-
-``osd_recovery_max_active_hdd``
-
-:Description: The number of active recovery requests per OSD at one time, if the
- primary device is rotational.
-
-:Type: 32-bit Integer
-:Default: ``3``
-
-``osd_recovery_max_active_ssd``
-
-:Description: The number of active recovery requests per OSD at one time, if the
- primary device is non-rotational (i.e., an SSD).
-
-:Type: 32-bit Integer
-:Default: ``10``
-
-
-``osd_recovery_max_chunk``
-
-:Description: The maximum size of a recovered chunk of data to push.
-:Type: 64-bit Unsigned Integer
-:Default: ``8 << 20``
-
-
-``osd_recovery_max_single_start``
-
-:Description: The maximum number of recovery operations per OSD that will be
- newly started when an OSD is recovering.
-:Type: 64-bit Unsigned Integer
-:Default: ``1``
-
-
-``osd_recovery_thread_timeout``
-
-:Description: The maximum time in seconds before timing out a recovery thread.
-:Type: 32-bit Integer
-:Default: ``30``
-
-
-``osd_recover_clone_overlap``
-
-:Description: Preserves clone overlap during recovery. Should always be set
- to ``true``.
-
-:Type: Boolean
-:Default: ``true``
-
-
-``osd_recovery_sleep``
-
-:Description: Time in seconds to sleep before the next recovery or backfill op.
- Increasing this value will slow down recovery operation while
- client operations will be less impacted.
-
-:Type: Float
-:Default: ``0``
-
-
-``osd_recovery_sleep_hdd``
-
-:Description: Time in seconds to sleep before next recovery or backfill op
- for HDDs.
-
-:Type: Float
-:Default: ``0.1``
-
-
-``osd_recovery_sleep_ssd``
-
-:Description: Time in seconds to sleep before the next recovery or backfill op
- for SSDs.
-
-:Type: Float
-:Default: ``0``
-
-
-``osd_recovery_sleep_hybrid``
-
-:Description: Time in seconds to sleep before the next recovery or backfill op
- when OSD data is on HDD and OSD journal / WAL+DB is on SSD.
-
-:Type: Float
-:Default: ``0.025``
-
-
-``osd_recovery_priority``
-
-:Description: The default priority set for recovery work queue. Not
- related to a pool's ``recovery_priority``.
-
-:Type: 32-bit Integer
-:Default: ``5``
-
+.. confval:: osd_recovery_delay_start
+.. confval:: osd_recovery_max_active
+.. confval:: osd_recovery_max_active_hdd
+.. confval:: osd_recovery_max_active_ssd
+.. confval:: osd_recovery_max_chunk
+.. confval:: osd_recovery_max_single_start
+.. confval:: osd_recover_clone_overlap
+.. confval:: osd_recovery_sleep
+.. confval:: osd_recovery_sleep_hdd
+.. confval:: osd_recovery_sleep_ssd
+.. confval:: osd_recovery_sleep_hybrid
+.. confval:: osd_recovery_priority
Tiering
=======
long_desc: There can be osd_max_backfills local reservations AND the same remote
reservations per OSD. So a value of 1 lets this OSD participate as 1 PG primary
in recovery and 1 shard of another recovering PG.
+ fmt_desc: The maximum number of backfills allowed to or from a single OSD.
+ Note that this is applied separately for read and write operations.
default: 1
flags:
- runtime
level: advanced
desc: how frequently to retry backfill reservations after being denied (e.g., due
to a full OSD)
+ fmt_desc: The number of seconds to wait before retrying backfill requests.
default: 30
with_legacy: true
- name: osd_recovery_retry_interval
type: bool
level: advanced
default: true
+ fmt_desc: Enable removing duplicates in the OSD map.
with_legacy: true
- name: osd_map_cache_size
type: int
level: advanced
default: 50
+ fmt_desc: The number of OSD maps to keep cached.
with_legacy: true
- name: osd_map_message_max
type: int
level: advanced
desc: maximum number of OSDMaps to include in a single message
+ fmt_desc: The maximum map entries allowed per MOSDMap message.
default: 40
with_legacy: true
- name: osd_map_message_max_bytes
type: bool
level: advanced
default: true
+ fmt_desc: Preserves clone overlap during recovery. Should always be set
+ to ``true``.
with_legacy: true
- name: osd_num_cache_shards
type: size
desc: which operation priority queue algorithm to use
long_desc: which operation priority queue algorithm to use; mclock_scheduler is
currently experimental
+ 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
+ (``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
see_also:
- osd_op_queue_cut_off
long_desc: the threshold between high priority ops that use strict priority ordering
and low priority ops that use a fairness algorithm that may or may not incorporate
priority
+ fmt_desc: This selects which priority ops will be sent to the strict
+ queue verses the normal queue. The ``low`` setting sends all
+ replication ops and higher to the strict queue, while the ``high``
+ option sends only replication acknowledgment ops and higher to
+ the strict queue. Setting this to ``high`` should help when a few
+ OSDs in the cluster are very busy especially when combined with
+ ``wpq`` in the ``osd_op_queue`` setting. OSDs that are very busy
+ handling replication traffic could starve primary client traffic
+ on these OSDs without these settings. Requires a restart.
default: high
see_also:
- osd_op_queue
level: advanced
desc: IO proportion reserved for each client (default)
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO proportion reserved for each client (default).
default: 1
see_also:
- osd_op_queue
level: advanced
desc: IO share for each client (default) over reservation
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO share for each client (default) over reservation.
default: 1
see_also:
- osd_op_queue
level: advanced
desc: IO limit for each client (default) over reservation
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO limit for each client (default) over reservation.
default: 999999
see_also:
- osd_op_queue
level: advanced
desc: IO proportion reserved for background recovery (default)
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO proportion reserved for background recovery (default).
default: 1
see_also:
- osd_op_queue
level: advanced
desc: IO share for each background recovery over reservation
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO share for each background recovery over reservation.
default: 1
see_also:
- osd_op_queue
level: advanced
desc: IO limit for background recovery over reservation
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO limit for background recovery over reservation.
default: 999999
see_also:
- osd_op_queue
level: advanced
desc: IO proportion reserved for background best_effort (default)
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO proportion reserved for background best_effort (default).
default: 1
see_also:
- osd_op_queue
level: advanced
desc: IO share for each background best_effort over reservation
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO share for each background best_effort over reservation.
default: 1
see_also:
- osd_op_queue
level: advanced
desc: IO limit for background best_effort over reservation
long_desc: Only considered for osd_op_queue = mclock_scheduler
+ fmt_desc: IO limit for background best_effort over reservation.
default: 999999
see_also:
- osd_op_queue
type: int
level: advanced
default: 64
+ fmt_desc: The minimum number of objects per backfill scan.
with_legacy: true
- name: osd_backfill_scan_max
type: int
level: advanced
default: 512
+ fmt_desc: The maximum number of objects per backfill scan.p
with_legacy: true
- name: osd_op_thread_timeout
type: int
level: advanced
default: 15
+ fmt_desc: The Ceph OSD Daemon operation thread timeout in seconds.
with_legacy: true
- name: osd_op_thread_suicide_timeout
type: int
type: float
level: advanced
desc: Time in seconds to sleep before next recovery or backfill op
+ fmt_desc: Time in seconds to sleep before the next recovery or backfill op.
+ Increasing this value will slow down recovery operation while
+ client operations will be less impacted.
default: 0
flags:
- runtime
type: float
level: advanced
desc: Time in seconds to sleep before next recovery or backfill op for HDDs
+ fmt_desc: Time in seconds to sleep before next recovery or backfill op
+ for HDDs.
default: 0.1
flags:
- runtime
type: float
level: advanced
desc: Time in seconds to sleep before next recovery or backfill op for SSDs
+ fmt_desc: Time in seconds to sleep before the next recovery or backfill op
+ for SSDs.
default: 0
see_also:
- osd_recovery_sleep
level: advanced
desc: Time in seconds to sleep before next recovery or backfill op when data is
on HDD and journal is on SSD
+ fmt_desc: Time in seconds to sleep before the next recovery or backfill op
+ when OSD data is on HDD and OSD journal / WAL+DB is on SSD.
default: 0.025
see_also:
- osd_recovery_sleep
type: float
level: advanced
desc: Time in seconds to sleep before next snap trim (overrides values below)
+ fmt_desc: Time in seconds to sleep before next snap trim op.
+ Increasing this value will slow down snap trimming.
+ This option overrides backend specific variants.
default: 0
with_legacy: true
- name: osd_snap_trim_sleep_hdd
type: float
level: advanced
desc: Time in seconds to sleep before next snap trim for SSDs
+ fmt_desc: Time in seconds to sleep before next snap trim op
+ for SSD OSDs (including NVMe).
default: 0
- name: osd_snap_trim_sleep_hybrid
type: float
level: advanced
desc: Time in seconds to sleep before next snap trim when data is on HDD and journal
is on SSD
+ fmt_desc: Time in seconds to sleep before next snap trim op
+ when OSD data is on an HDD and the OSD journal or WAL+DB is on an SSD.
default: 2
- name: osd_scrub_invalid_stats
type: bool
type: float
level: advanced
default: 0
+ fmt_desc: After peering completes, Ceph will delay for the specified number
+ of seconds before starting to recover RADOS objects.
with_legacy: true
- name: osd_recovery_max_active
type: uint
level: advanced
desc: Number of simultaneous active recovery operations per OSD (overrides _ssd
and _hdd if non-zero)
+ fmt_desc: The number of active recovery requests per OSD at one time. More
+ requests will accelerate recovery, but the requests places an
+ increased load on the cluster.
+ note: This value is only used if it is non-zero. Normally it
+ is ``0``, which means that the ``hdd`` or ``ssd`` values
+ (below) are used, depending on the type of the primary
+ device backing the OSD.
default: 0
see_also:
- osd_recovery_max_active_hdd
level: advanced
desc: Number of simultaneous active recovery operations per OSD (for rotational
devices)
+ fmt_desc: The number of active recovery requests per OSD at one time, if the
+ primary device is rotational.
default: 3
see_also:
- osd_recovery_max_active
level: advanced
desc: Number of simultaneous active recovery operations per OSD (for non-rotational
solid state devices)
+ fmt_desc: The number of active recovery requests per OSD at one time, if the
+ primary device is non-rotational (i.e., an SSD).
default: 10
see_also:
- osd_recovery_max_active
type: uint
level: advanced
default: 1
+ fmt_desc: The maximum number of recovery operations per OSD that will be
+ newly started when an OSD is recovering.
with_legacy: true
# max size of push chunk
- name: osd_recovery_max_chunk
type: size
level: advanced
default: 8_M
+ fmt_desc: the maximum total size of data chunks a recovery op can carry.
with_legacy: true
# max number of omap entries per chunk; 0 to disable limit
- name: osd_recovery_max_omap_entries_per_chunk
type: size
level: advanced
default: 1000
+ fmt_desc: the overhead for serving a push op
with_legacy: true
# max size of push message
- name: osd_max_push_cost
type: float
level: advanced
default: 30
+ fmt_desc: An operation becomes complaint worthy after the specified number
+ of seconds have elapsed.
with_legacy: true
- name: osd_command_max_records
type: int
type: int
level: advanced
default: 5
+ fmt_desc: How many operations logs to display at once.
with_legacy: true
- name: osd_backoff_on_unfound
type: bool
type: uint
level: advanced
default: 20
+ fmt_desc: The maximum number of completed operations to track.
with_legacy: true
# Oldest completed op to track
- name: osd_op_history_duration
type: uint
level: advanced
default: 600
+ fmt_desc: The oldest completed operation to track.
with_legacy: true
# Max number of slow ops to track
- name: osd_op_history_slow_op_size
type: uint
level: advanced
default: 63
+ fmt_desc: The priority set for client operations. This value is relative
+ to that of ``osd_recovery_op_priority`` below. The default
+ strongly favors client ops over recovery.
with_legacy: true
- name: osd_recovery_op_priority
type: uint
level: advanced
desc: Priority to use for recovery operations if not specified for the pool
- fmt_desc: Default priority used for recovery operations if pool doesn't override.
+ fmt_desc: The priority of recovery operations vs client operations, if not specified by the
+ pool's ``recovery_op_priority``. The default value prioritizes client
+ ops (see above) over recovery ops. You may adjust the tradeoff of client
+ impact against the time to restore cluster health by lowering this value
+ for increased prioritization of client ops, or by increasing it to favor
+ recovery.
default: 3
with_legacy: true
- name: osd_peering_op_priority
type: uint
level: advanced
default: 5
+ fmt_desc: The priority set for the snap trim work queue.
with_legacy: true
- name: osd_snap_trim_cost
type: size
type: uint
level: advanced
desc: Priority for scrub operations in work queue
+ fmt_desc: The default work queue priority for scheduled scrubs when the
+ pool doesn't specify a value of ``scrub_priority``. This can be
+ boosted to the value of ``osd_client_op_priority`` when scrubs are
+ blocking client operations.
default: 5
with_legacy: true
- name: osd_scrub_cost
type: uint
level: advanced
default: 120
+ fmt_desc: The priority set for user requested scrub on the work queue. If
+ this value were to be smaller than ``osd_client_op_priority`` it
+ can be boosted to the value of ``osd_client_op_priority`` when
+ scrub is blocking client operations.
with_legacy: true
- name: osd_recovery_priority
type: uint
level: advanced
desc: Priority of recovery in the work queue
long_desc: Not related to a pool's recovery_priority
+ fmt_desc: The default priority set for recovery work queue. Not
+ related to a pool's ``recovery_priority``.
default: 5
with_legacy: true
# set default cost equal to 20MB io
projects / ceph.git / commitdiff