Skip to content

Commit 57d680e

Browse files
authored
Strengthened warning against multiple arbiters: (#999)
1 parent df382b6 commit 57d680e

File tree

3 files changed

+8
-7
lines changed

3 files changed

+8
-7
lines changed

source/core/replica-set-arbiter.txt

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,17 +58,18 @@ Replica Set Protocol Version and Arbiter
5858

5959
.. _rollbacks-multi-arbiters:
6060

61-
Concerns with Multiple Arbiters
62-
-------------------------------
61+
Don't Deploy Multiple Arbiters
62+
------------------------------
6363

6464
Use a single arbiter to avoid problems with data consistency. Multiple
65-
arbiters prevent the reliable use of the majority write concern.
65+
arbiters prevent the reliable use of the majority
66+
:ref:`write concern <write-concern>`.
6667

6768
To ensure that a write will persist after the failure of a primary node,
6869
the majority write concern requires a majority of nodes to acknowledge
6970
a write operation. Arbiters do not store any data, but they do
7071
contribute to the number of nodes in a replica set. When a replica set
71-
has multiple arbiters it is less likely that a majority of data bearing
72+
has multiple arbiters, it's less likely that a majority of data bearing
7273
nodes will be available after a node failure.
7374

7475
.. warning::
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
.. warning::
22

3-
Avoid deploying more than one arbiter per replica set.
3+
Don't deploy more than one arbiter per replica set.
44

55
See also: :ref:`rollbacks-multi-arbiters`
66

source/tutorial/add-replica-set-arbiter.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,12 @@ Add an Arbiter to Replica Set
1010
:depth: 1
1111
:class: singlecol
1212

13-
In some circumstances (such as you have a primary and a secondary but
13+
In some circumstances (such as if you have a primary and a secondary but
1414
cost constraints prohibit adding another secondary), you may choose to
1515
add a :binary:`~bin.mongod` instance to a replica set as an
1616
:doc:`arbiter </core/replica-set-arbiter>` to vote in elections.
1717

18-
Arbiters are :binary:`~bin.mongod` instances that are part of a
18+
Arbiters are ``mongod`` instances that are part of a
1919
:term:`replica set` but do not hold data (i.e. do not provide data
2020
redundancy). They can, however, participate in :ref:`elections
2121
<replica-set-elections>`.

0 commit comments

Comments
 (0)