Skip to content

Commit 5d76811

Browse files
committed
DOCS-12122: blurb about psa and cache pressure w read concern majority
1 parent 96a9159 commit 5d76811

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

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

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,24 @@ server or a monitoring host.
2525
Considerations
2626
--------------
2727

28+
Read Concern ``majority`` and Three-Member PSA
29+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30+
31+
.. admonition:: For 3-Member Primary-Secondary-Arbiter Architecture*
32+
:class: warning
33+
34+
If you have a three-member replica set with a
35+
primary-secondary-arbiter (PSA) architecture or a sharded cluster
36+
with a three-member PSA shards, the cache pressure will increase if
37+
any data bearing node is down and support for
38+
:readconcern:`"majority"` read concern is enabled.
39+
40+
To prevent the storage cache pressure from immobilizing a deployment
41+
with a three-member primary-secondary-arbiter (PSA) architecture,
42+
you can disable read concern "majority" for MongoDB 4.0.3+
43+
and 3.6.1+. For more information, see
44+
:ref:`4.0-disable-read-concern-majority`.
45+
2846
Replica Set Protocol Version
2947
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3048

@@ -40,6 +58,7 @@ process is added to the replica set, the arbiter will act like any other
4058
:binary:`~bin.mongod` process and start up with a set of data files and with a
4159
full-sized :term:`journal`.
4260

61+
4362
IP Binding
4463
~~~~~~~~~~
4564

0 commit comments

Comments
 (0)