From 7300fb24bb1cb781f26dfa0e2d8fd0f7b61053bf Mon Sep 17 00:00:00 2001 From: Anthony D'Atri Date: Tue, 6 May 2025 12:42:18 -0400 Subject: [PATCH] doc/cephadm: Correct formatting in upgrade.rst Signed-off-by: Anthony D'Atri (cherry picked from commit 0e1adc4ae69b9fdc8f4a8480f3e498efa06520f4) --- doc/cephadm/upgrade.rst | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/doc/cephadm/upgrade.rst b/doc/cephadm/upgrade.rst index fed7f779845cd..dddb5d46ad55a 100644 --- a/doc/cephadm/upgrade.rst +++ b/doc/cephadm/upgrade.rst @@ -28,16 +28,18 @@ The automated upgrade process follows Ceph best practices. For example: disabling the autoscaler for the duration of the upgrade. This is so that PG splitting or merging in the middle of an upgrade does not unduly delay upgrade progress. In a very large cluster this could easily increase the - time to complete by a whole day or more, especially if the upgrade happens to - change PG autoscaler behavior by e.g. changing the default value of - the :confval:`mon_target_pg_per_osd`. - | - * ``ceph osd pool set noautoscale`` - * Perform the upgrade - * ``ceph osd pool unset noautoscale`` - | + time to complete by a day or more, especially if the upgrade happens to + change PG autoscaler behavior by e.g. changing the default value + of :confval:`mon_target_pg_per_osd`. + + .. prompt:: bash # + + ceph osd pool set noautoscale + # Perform the upgrade + ceph osd pool unset noautoscale + When pausing autoscaler activity in this fashion, the existing values for - each pool's mode, ``off``, ``on``, or ``warn`` are expected to remain. + each pool's mode, ``off``, ``on``, or ``warn``, are expected to remain. If the new release changes the above target value, there may be splitting or merging of PGs when unsetting after the upgrade. -- 2.39.5