doc/health-checks: update MON_NETSPLIT documentation

Update the MON_NETSPLIT health check documentation to reflect the
introduction of the configurable mon_netsplit_grace_period option.

Fixes: https://tracker.ceph.com/issues/71344
Signed-off-by: Kamoltat Sirivadhna <ksirivad@redhat.com>

diff --git a/doc/rados/operations/health-checks.rst b/doc/rados/operations/health-checks.rst
index 7231d9c1a35cb149b6394f8c52040a866f2ffd83..bc2311e2e0faa88bc48905aa269e36dc4b0cb3d7 100644 (file)
--- a/doc/rados/operations/health-checks.rst
+++ b/doc/rados/operations/health-checks.rst
@@ -163,6 +163,12 @@ which are frequently updated. This warning only appears when
 the cluster is provisioned with at least three Ceph Monitors and are using the
 ``connectivity`` election strategy.
 
+To reduce false alarms from transient network issues, detected netsplits are
+not immediately reported as health warnings. Instead, they must persist for at
+least ``mon_netsplit_grace_period`` seconds (default: 9 seconds) before being
+reported. If the network partition resolves within this grace period, no health
+warning is emitted.
+
 Network partitions are reported in two ways:
 
 - As location-level netsplits (e.g., "Netsplit detected between dc1 and dc2") when
@@ -173,6 +179,18 @@ Network partitions are reported in two ways:
 The system prioritizes reporting at the highest topology level (``datacenter``, ``rack``, etc.)
 when possible, to better help operators identify infrastructure-level network issues.
 
+To adjust the grace period threshold, run the following command:
+
+.. prompt:: bash $
+
+   ceph config set mon mon_netsplit_grace_period <seconds>
+
+To disable the grace period entirely (immediate reporting), set the value to 0:
+
+.. prompt:: bash $
+
+   ceph config set mon mon_netsplit_grace_period 0
+
 AUTH_INSECURE_GLOBAL_ID_RECLAIM
 _______________________________