Skip to content

Commit 0000563

Browse files
authored
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
1 parent a9eabb8 commit 0000563

File tree

6 files changed

+68
-2
lines changed

6 files changed

+68
-2
lines changed

source/core/replica-set-arbiter.txt

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,23 @@ nodes will be available after a node failure.
7474

7575
To avoid this scenario, use at most a single arbiter.
7676

77+
.. versionadded:: 5.3
78+
79+
Starting in MongoDB 5.3, support for multiple arbiters in a replica set is
80+
disabled by default. If you attempt to add multiple arbiters to a
81+
replica set, the server returns an error:
82+
83+
.. code-block:: text
84+
:copyable: false
85+
86+
MongoServerError: Multiple arbiters are not allowed unless all nodes
87+
were started with --setParameter 'allowMultipleArbiters=true'
88+
89+
To add multiple arbiters to a replica set using MongoDB 5.3 or later, start
90+
each node with the :parameter:`allowMultipleArbiters` parameter set to ``true``:
91+
92+
.. include:: /includes/setParameter-allowMultipleArbiters.rst
93+
7794
Security
7895
--------
7996

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
.. code-block:: bash
2+
3+
mongod --setParameter allowMultipleArbiters=true
4+
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
2+
Starting in MongoDB 5.3, support for multiple arbiters in a replica set is
3+
disabled by default. To enable support for multiple arbiters, start each
4+
node with the :parameter:`allowMultipleArbiters` parameter.
5+

source/reference/parameters.txt

Lines changed: 32 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1752,13 +1752,13 @@ Logging Parameters
17521752

17531753
*Default*: 10
17541754

1755-
Specifies the maxium size, in kilobytes, for an individual
1755+
Specifies the maximum size, in kilobytes, for an individual
17561756
attribute field in a log entry; attributes exceeding this limit are
17571757
truncated.
17581758

17591759
Truncated attribute fields print field content up to the
17601760
:parameter:`maxLogSizeKB` limit and excise field content past that
1761-
limit, retaining valid JSON formating. Log entires that contain
1761+
limit, retaining valid JSON formatting. Log entries that contain
17621762
truncated attributes append a ``truncated`` object to the end of the
17631763
log entry.
17641764

@@ -2784,6 +2784,36 @@ If you attempt to update ``disableSplitHorizonIPCheck`` at runtime,
27842784

27852785
db.adminCommand( { setParameter: 1, mirrorReads: { samplingRate: 0.10 } } )
27862786

2787+
.. parameter:: allowMultipleArbiters
2788+
2789+
|mongod-only|
2790+
2791+
.. versionadded:: 5.3
2792+
2793+
*Type*: boolean
2794+
2795+
*Default*: false
2796+
2797+
Specifies whether the replica set allows the use of multiple arbiters.
2798+
2799+
The use of multiple arbiters is not recommended:
2800+
2801+
- Multiple arbiters prevent the reliable use of the majority write concern.
2802+
MongoDB counts arbiters in calculating a membership majority, but arbiters
2803+
do not store data. With the inclusion of multiple arbiters, it's possible
2804+
for a majority write operation to return success before the write replicates
2805+
to a majority of data bearing nodes.
2806+
2807+
- Multiple arbiters allow replica sets to accept writes even when the
2808+
replica set doesn't have sufficient secondaries for data replication.
2809+
2810+
For more information, see
2811+
:ref:`Concerns with Multiple Arbiters <rollbacks-multi-arbiters>`.
2812+
2813+
The parameter can only be set during startup:
2814+
2815+
.. include:: /includes/setParameter-allowMultipleArbiters.rst
2816+
27872817
Sharding Parameters
27882818
~~~~~~~~~~~~~~~~~~~
27892819

source/release-notes/5.3-compatibility.txt

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,11 @@ Intra-Cluster Authentication
3636

3737
.. include:: /includes/intra-cluster-authentication.rst
3838

39+
Multiple Arbiters
40+
------------------
41+
42+
.. include:: /includes/support-multiple-arbiters.rst
43+
3944
Default db.stat() Settings
4045
--------------------------
4146
Starting in MongoDB 5.3.0, 5.2.1, and 5.0.6, the :dbcommand:`dbStats`

source/release-notes/5.3.txt

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -175,6 +175,11 @@ Starting in MongoDB 5.3, you can use the :pipeline:`$geoNear` pipeline
175175
operator on any field in a :ref:`time series collection
176176
<manual-timeseries-collection>`.
177177

178+
Multiple Arbiters
179+
~~~~~~~~~~~~~~~~~~
180+
181+
.. include:: /includes/support-multiple-arbiters.rst
182+
178183
Report an Issue
179184
---------------
180185

0 commit comments

Comments
 (0)