(DOCSP-41494) Add a note to forced recovery of appdb about possible data loss (#1978)

* (DOCSP-41494) Add a note to forced recovery of appdb about possible data loss

Author: JuliaMongo

source/tutorial/recover-appdb-forced-reconfig.txt

@@ -4,8 +4,16 @@
 Recover the {+appdb+} if its Replica Set Loses Majority
 ======================================================================
 
+.. facet::
+   :name: genre
+   :values: tutorial
+
 .. default-domain:: mongodb
 
+.. meta::
+   :keywords: forced recovery, application database, majority, primary election
+   :description: How to configure the application database in your Kubernetes deployment to recover and elect a primary if it loses majority.
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -18,6 +26,7 @@ the |k8s-op-short| doesn't automatically trigger a forced replica set reconfigur
 You must manually initiate a forced replica set reconfiguration and restore
 the {+appdb+} replica set to a healthy state.
 
+
 Overview
 ---------
 
@@ -41,6 +50,13 @@ current (latest) :opsmgr:`Automation Configuration version </reference/api/autom
 Using the flag allows the |k8s-op-short| to reconfigure the replica set in
 case a primary node isn't elected.
 
+.. important::
+
+   Forced reconfiguration of the {+appdb+} can result in undesired behavior,
+   including :manual:`rollback </core/replica-set-rollbacks/#std-label-replica-set-rollbacks/>`
+   of :manual:`"majority" </reference/write-concern/#mongodb-writeconcern-writeconcern.-majority-/>`
+   committed writes, which could lead to an unexpected data loss.
+
 Recover the {+appdb+} through a Forced Reconfiguration
 ------------------------------------------------------------------