DOCS-15125-compact-maintenance-mode (#880)

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

* DOCS-15125-compact-maintenance-mode

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/reference/command/compact.txt

@@ -226,7 +226,23 @@ Replica Sets
 - Ideally run :dbcommand:`compact` on a secondary. See option
   ``force`` above for information regarding compacting the primary.
 
-.. include:: /includes/extracts/fact-command-puts-secondary-into-recovering-compact.rst
+- Starting in MongoDB 5.1 (and 5.0.3, 4.4.9, and 4.2.18): a secondary is
+  not available when :dbcommand:`compact` is running. The secondary does
+  not enter the :replstate:`RECOVERING` state.
+
+- For other MongoDB versions: on secondaries, :dbcommand:`compact`
+  forces the secondary to enter the :replstate:`RECOVERING` state. Read
+  operations issued to an instance in the :replstate:`RECOVERING` state
+  will fail. This prevents clients from reading during the operation.
+  When the operation completes, the secondary returns to
+  :replstate:`SECONDARY` state.
+
+See :doc:`/reference/replica-states/` for more information about replica
+set member states.
+
+See :doc:`/tutorial/perform-maintence-on-replica-set-members` for an
+example replica set maintenance procedure to maximize availability
+during maintenance operations.
 
 Sharded Clusters
 ~~~~~~~~~~~~~~~~