rgw/lc: Warn against changing rgw_lc_max_objs once lifecycle is in use

Each bucket's lifecycle entry is hashed onto a shard by this count, so
changing it remaps existing entries and can leave duplicates behind.

Signed-off-by: Matthew N. Heler <matthew.heler@hotmail.com>
(cherry picked from commit 83189af8e663d867649d003afaa9d1cf09c88391)

diff --git a/src/common/options/rgw.yaml.in b/src/common/options/rgw.yaml.in
index 90ea9f156521facabea47e49c93ba2896866c793..64a24526ca66d148fa441ab6ad3cefb8a298ea7b 100644 (file)
--- a/src/common/options/rgw.yaml.in
+++ b/src/common/options/rgw.yaml.in
@@ -455,7 +455,8 @@ options:
   level: advanced
   desc: Number of lifecycle data shards
   long_desc: Number of RADOS objects to use for storing lifecycle index. This affects
-    concurrency of lifecycle maintenance, as shards can be processed in parallel.
+    concurrency of lifecycle maintenance, as shards can be processed in parallel. Do not
+    change this value after deployment unless `radosgw-admin lc list` is empty.
   default: 32
   services:
   - rgw