From 7479ed8f19141a40090924d24557e97dc13391b3 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Laimis=20Juzeli=C5=ABnas?= Date: Thu, 9 Jan 2025 00:05:34 +0200 Subject: [PATCH] doc/radosgw/config-ref: fix lc worker thread tuning This commit updates RGW Config Reference - Lifecycle Settings section. In particular it addresses an incorrect suggestion to decrease parallel threads in the workers pool for a more aggressive/accelerated per-bucket lifecycle processing. A more aggressive lifecycle processing for a bucket containing higher number of objects is achieved by increasing, not decreasing parallel threads. Current suggestion is miss-leading. Fixes: https://tracker.ceph.com/issues/63659 Signed-off-by: Laimis Juzeliunas (cherry picked from commit b7ae18a292c7d1d5139dfb74c575f1af0de29a3e) --- doc/radosgw/config-ref.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/radosgw/config-ref.rst b/doc/radosgw/config-ref.rst index b183c3b997eca..6017a037b1d8d 100644 --- a/doc/radosgw/config-ref.rst +++ b/doc/radosgw/config-ref.rst @@ -75,7 +75,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. -- 2.39.5