doc/rados/operations/health-checks: Add LARGE_OMAP_OBJECTS

Document LARGE_OMAP_OBJECTS health check

Signed-off-by: Brad Hubbard <bhubbard@redhat.com>

diff --git a/doc/rados/operations/health-checks.rst b/doc/rados/operations/health-checks.rst
index 1fdd72badd347bb6eb5da86b0bb39461480f7c56..256765f6878ecdf4ffe54d82b82a585e806b84ef 100644 (file)
--- a/doc/rados/operations/health-checks.rst
+++ b/doc/rados/operations/health-checks.rst
@@ -396,6 +396,25 @@ paired with *PG_DAMAGED* (see above).
 
 See :doc:`pg-repair` for more information.
 
+LARGE_OMAP_OBJECTS
+__________________
+
+One or more pools contain large omap objects as determined by
+``osd_deep_scrub_large_omap_object_key_threshold`` (threshold for number of keys
+to determine a large omap object) or
+``osd_deep_scrub_large_omap_object_value_sum_threshold`` (the threshold for
+summed size (bytes) of all key values to determine a large omap object) or both.
+More information on the object name, key count, and size in bytes can be found
+by searching the cluster log for 'Large omap object found'. Large omap objects
+can be caused by RGW bucket index objects that do not have automatic resharding
+enabled. Please see :ref:`RGW Dynamic Bucket Index Resharding
+<rgw_dynamic_bucket_index_resharding>` for more information on resharding.
+
+The thresholds can be adjusted with::
+
+  ceph config set osd osd_deep_scrub_large_omap_object_key_threshold <keys>
+  ceph config set osd osd_deep_scrub_large_omap_object_value_sum_threshold <bytes>
+
 CACHE_POOL_NEAR_FULL
 ____________________
 

diff --git a/doc/radosgw/dynamicresharding.rst b/doc/radosgw/dynamicresharding.rst
index 8dfb815519546fe4ba7c69de62b08ebe394321b2..4d51cd76ebc5c7818200c3292ab9121eaa560eee 100644 (file)
--- a/doc/radosgw/dynamicresharding.rst
+++ b/doc/radosgw/dynamicresharding.rst
@@ -1,3 +1,5 @@
+.. _rgw_dynamic_bucket_index_resharding:
+
 ===================================
 RGW Dynamic Bucket Index Resharding
 ===================================