From b239a8b90abfbd1a660a961dd92e1fecbf13fb9f Mon Sep 17 00:00:00 2001 From: Ilya Dryomov Date: Wed, 7 Jun 2023 21:34:07 +0200 Subject: [PATCH] doc: drop mention of rbd_mirror_journal_max_fetch_bytes option It was removed in commit 1ef12ea0d29f ("rbd-mirror: remove rbd_mirror_journal_max_fetch_bytes option") in 2019. Commit 32375cb789d7 ("doc: misc clarity and capitalization") added a "tip" mentioning it in 2020 in an attempt to capture advice [1]. [1] https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/IHMGNFLWCD5E5R4W5S2BSSKEB5X3N4S4/ Signed-off-by: Ilya Dryomov --- doc/rbd/rbd-mirroring.rst | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/doc/rbd/rbd-mirroring.rst b/doc/rbd/rbd-mirroring.rst index 74a2a364e8d0..2c9cc1b66bf8 100644 --- a/doc/rbd/rbd-mirroring.rst +++ b/doc/rbd/rbd-mirroring.rst @@ -304,11 +304,10 @@ For example:: .. tip:: ``rbd-mirror`` tunables are set by default to values suitable for mirroring an entire pool. When using ``rbd-mirror`` to migrate single - volumes been clusters you may achieve substantial performance gains - by setting ``rbd_mirror_journal_max_fetch_bytes=33554432`` and - ``rbd_journal_max_payload_bytes=8388608`` within the ``[client]`` config - section of the local or centralized configuration. Note that these - settings may allow ``rbd-mirror`` to present a substantial write workload + volumes between clusters you may achieve substantial performance gains + by setting ``rbd_journal_max_payload_bytes=8388608`` within the ``[client]`` + config section of the local or centralized configuration. Note that this + setting may allow ``rbd-mirror`` to present a substantial write workload to the destination cluster: monitor cluster performance closely during migrations and test carefully before running multiple migrations in parallel. -- 2.47.3