doc: osd_op_queue & osd_op_queue_cut_off
osd_op_queue default is: `prio`. Real is `wpq`. So this is a doc's bug.
If I understand properly: if osd_op_queue `wpq`, osd_op_queue_cut_off should be `high`. Real is `low`. This negative impact for queue or all as designed?
#1 Updated by Patrick Donnelly almost 3 years ago
- Tracker changed from Support to Documentation
- Project changed from Ceph to RADOS
- Subject changed from osd_op_queue & osd_op_queue_cut_off to doc: osd_op_queue & osd_op_queue_cut_off
- Category deleted (
- Target version deleted (
- Release deleted (
- Affected Versions deleted (
#2 Updated by Anthony D'Atri 3 months ago
The default value for `osd_op_queue_cutoff` changed to `high` with Octopus and was documented as such.
The default for `osd_op_queue` in `options.cc` appears to have `wpq` back at least as far as Luminous.
Luminous and Mimic `doc/rados/configuration/osd-config-ref.rst` claim `prio`; the docs were updated to `wpq` with the Nautilus release.
@zdover23 So I think there's nothing left to do here.