DOCS-15092 allowMultipleArbiters Parameter (#971) (#1031)

* DOCS-15092 Transfer from v6.0 branch

* DOCS-15092 Fixes per Jason Price

* DOCS-15092 Fixes per Jason Price

* DOCS-15092 Fixes per Jason Price

* DOCS-15092 Fixes per Jason Price

* DOCS-15092 Fixes per Jason Price

* DOCS-15092 Spelling

* DOCSP-15108 Fixes per Jason Price

* DOCSP-15108 Fixes per Jason Price

* DOCSP-15108 Fixes per Jason Price

* DOCS-15092 Fixes per Jason Price

* DOCSP-15108 Fixes per Jason Price

* DOCSP-15108 Fixes per Jason Price

Author: kennethdyer

source/core/replica-set-arbiter.txt

@@ -74,6 +74,23 @@ nodes will be available after a node failure.
 
    To avoid this scenario, use at most a single arbiter.
 
+.. versionadded:: 5.3
+
+Starting in MongoDB 5.3, support for multiple arbiters in a replica set is
+disabled by default. If you attempt to add multiple arbiters to a
+replica set, the server returns an error:
+
+.. code-block:: text
+   :copyable: false
+
+   MongoServerError: Multiple arbiters are not allowed unless all nodes
+   were started with --setParameter 'allowMultipleArbiters=true'
+
+To add multiple arbiters to a replica set using MongoDB 5.3 or later, start
+each node with the :parameter:`allowMultipleArbiters` parameter set to ``true``:
+
+.. include:: /includes/setParameter-allowMultipleArbiters.rst
+
 Security
 --------
 

source/includes/setParameter-allowMultipleArbiters.rst

@@ -0,0 +1,4 @@
+.. code-block:: bash
+
+   mongod --setParameter allowMultipleArbiters=true
+

source/includes/support-multiple-arbiters.rst

@@ -0,0 +1,5 @@
+
+Starting in MongoDB 5.3, support for multiple arbiters in a replica set is
+disabled by default. To enable support for multiple arbiters, start each
+node with the :parameter:`allowMultipleArbiters` parameter.
+

source/reference/parameters.txt

@@ -1752,13 +1752,13 @@ Logging Parameters
 
    *Default*: 10
 
-   Specifies the maxium size, in kilobytes, for an individual
+   Specifies the maximum size, in kilobytes, for an individual
    attribute field in a log entry; attributes exceeding this limit are
    truncated.
 
    Truncated attribute fields print field content up to the
    :parameter:`maxLogSizeKB` limit and excise field content past that
-   limit, retaining valid JSON formating. Log entires that contain
+   limit, retaining valid JSON formatting. Log entries that contain
    truncated attributes append a ``truncated`` object to the end of the
    log entry.
 
@@ -2784,6 +2784,36 @@ If you attempt to update ``disableSplitHorizonIPCheck`` at runtime,
 
       db.adminCommand( { setParameter: 1, mirrorReads: { samplingRate: 0.10 } } )
 
+.. parameter:: allowMultipleArbiters
+
+   |mongod-only|
+
+   .. versionadded:: 5.3
+
+   *Type*: boolean
+
+   *Default*: false
+
+   Specifies whether the replica set allows the use of multiple arbiters.
+
+   The use of multiple arbiters is not recommended:
+
+   - Multiple arbiters prevent the reliable use of the majority write concern.
+     MongoDB counts arbiters in calculating a membership majority, but arbiters
+     do not store data. With the inclusion of multiple arbiters, it's possible
+     for a majority write operation to return success before the write replicates
+     to a majority of data bearing nodes.
+
+   - Multiple arbiters allow replica sets to accept writes even when the
+     replica set doesn't have sufficient secondaries for data replication.
+
+   For more information, see
+   :ref:`Concerns with Multiple Arbiters <rollbacks-multi-arbiters>`.
+
+   The parameter can only be set during startup:
+
+   .. include:: /includes/setParameter-allowMultipleArbiters.rst
+
 Sharding Parameters
 ~~~~~~~~~~~~~~~~~~~
 

source/release-notes/5.3-compatibility.txt

@@ -36,6 +36,11 @@ Intra-Cluster Authentication
 
 .. include:: /includes/intra-cluster-authentication.rst
 
+Multiple Arbiters
+------------------
+
+.. include:: /includes/support-multiple-arbiters.rst
+
 Default db.stat() Settings
 --------------------------
 Starting in MongoDB 5.3.0, 5.2.1, and 5.0.6, the :dbcommand:`dbStats`

source/release-notes/5.3.txt

@@ -175,6 +175,11 @@ Starting in MongoDB 5.3, you can use the :pipeline:`$geoNear` pipeline
 operator on any field in a :ref:`time series collection
 <manual-timeseries-collection>`.
 
+Multiple Arbiters
+~~~~~~~~~~~~~~~~~~
+
+.. include:: /includes/support-multiple-arbiters.rst
+
 Report an Issue
 ---------------