summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAnthony D'Atri <anthonyeleven@users.noreply.github.com>2025-01-13 15:10:01 +0100
committerGitHub <noreply@github.com>2025-01-13 15:10:01 +0100
commit2ceb7a652f5b71c279707a7824c7b40e7e6b3617 (patch)
tree1d943a1ab5b39edb601f993320726d0311e432e5
parentMerge pull request #58924 from imtzw/tzw_ikey_lat (diff)
parentdoc/radosgw/config-ref: fix lc worker thread tuning (diff)
downloadceph-2ceb7a652f5b71c279707a7824c7b40e7e6b3617.tar.xz
ceph-2ceb7a652f5b71c279707a7824c7b40e7e6b3617.zip
Merge pull request #61272 from laimis9133/main
doc/radosgw/config-ref: fix lc worker thread tuning
-rw-r--r--doc/radosgw/config-ref.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/radosgw/config-ref.rst b/doc/radosgw/config-ref.rst
index edc6a90b0f9..b4aa56fff54 100644
--- a/doc/radosgw/config-ref.rst
+++ b/doc/radosgw/config-ref.rst
@@ -78,7 +78,7 @@ These values can be tuned based upon your specific workload to further increase
aggressiveness of lifecycle processing. For a workload with a larger number of buckets (thousands)
you would look at increasing the :confval:`rgw_lc_max_worker` value from the default value of 3 whereas for a
workload with a smaller number of buckets but higher number of objects (hundreds of thousands)
-per bucket you would consider decreasing :confval:`rgw_lc_max_wp_worker` from the default value of 3.
+per bucket you would consider increasing :confval:`rgw_lc_max_wp_worker` from the default value of 3.
.. note:: When looking to tune either of these specific values please validate the
current Cluster performance and Ceph Object Gateway utilization before increasing.