(DOCS-13394): Deprecate getLastErrorDefaults custom values

Author: jeff-allen-mongo

source/includes/extracts-4.4-changes.yaml

@@ -499,4 +499,15 @@ content: |
 
   Starting in version 4.4, MongoDB ignores the :ref:`verbose
   <cmd-mapreduce-verbose>` option.
+---
+ref: 4.4-changes-getLastErrorDefaults-deprecation
+content: |
+
+  Starting in version 4.4, MongoDB deprecates specifying a
+  :rsconf:`settings.getLastErrorDefaults` value other than the default
+  of ``{ w: 1, wtimeout: 0 }``. MongoDB 4.4 honors any write concern
+  value that you specify, however future MongoDB versions might not
+  honor values other than the default. Instead, use the
+  :dbcommand:`setDefaultRWConcern` command to set the default read or
+  write concern configuration for a replica set or sharded cluster.
 ...

source/reference/replica-configuration.txt

@@ -473,6 +473,10 @@ Replica Set Configuration Fields
       not set, the default write concern for the replica set only
       requires confirmation from the primary.
 
+      .. important::
+
+         .. include:: /includes/extracts/4.4-changes-getLastErrorDefaults-deprecation.rst
+
    .. rsconf::  settings.getLastErrorModes
 
       *Optional*.

source/release-notes/4.4-compatibility.txt

@@ -61,6 +61,11 @@ Initial Sync Restrictions on Operations
 
 .. include:: /includes/extracts/4.4-changes-repl-state-restrictions.rst
 
+Custom ``getLastErrorDefaults`` Values Deprecated
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ 
+.. include:: /includes/extracts/4.4-changes-getLastErrorDefaults-deprecation.rst
+
 Projection Compatibility Changes
 --------------------------------