diff --git a/source/administration/production-notes.txt b/source/administration/production-notes.txt index 3347566e9a4..09360f1798c 100644 --- a/source/administration/production-notes.txt +++ b/source/administration/production-notes.txt @@ -198,8 +198,6 @@ Read Concern .. include:: /includes/fact-read-own-writes.rst -.. include:: /includes/fact-enable-majority-readConcern.rst - Write Concern ~~~~~~~~~~~~~ diff --git a/source/core/replica-set-arbiter.txt b/source/core/replica-set-arbiter.txt index 3ecf619397e..7f55c726670 100644 --- a/source/core/replica-set-arbiter.txt +++ b/source/core/replica-set-arbiter.txt @@ -48,24 +48,6 @@ number of votes to break a tie: .. end-content-even-votes-example -Read Concern ``majority`` and Three-Member PSA ----------------------------------------------- - -.. warning:: For 3-Member Primary-Secondary-Arbiter Architecture* - - - If you have a three-member replica set with a - primary-secondary-arbiter (PSA) architecture or a sharded cluster - with a three-member PSA shards, the cache pressure will increase if - any data bearing node is down and support for - :readconcern:`"majority"` read concern is enabled. - - To prevent the storage cache pressure from immobilizing a deployment - with a three-member primary-secondary-arbiter (PSA) architecture, - you can disable read concern "majority" starting in MongoDB 4.0.3 - (and 3.6.1+). For more information, see - :ref:`disable-read-concern-majority`. - Replica Set Protocol Version and Arbiter ----------------------------------------- diff --git a/source/core/transactions-production-consideration.txt b/source/core/transactions-production-consideration.txt index 1c2a13d924c..5509e137c4a 100644 --- a/source/core/transactions-production-consideration.txt +++ b/source/core/transactions-production-consideration.txt @@ -147,37 +147,6 @@ Sharded Clusters and Arbiters .. include:: /includes/extracts/transactions-arbiters.rst -.. |disabledrcmaj| replace:: :ref:`transactions-psa` - -.. _transactions-psa: - -3-Member Primary-Secondary-Arbiter Architecture ------------------------------------------------ - -For a three-member replica set with a primary-secondary-arbiter (PSA) -architecture or a sharded cluster with a three-member PSA shards, you -may have :ref:`disabled read concern "majority" -` to avoid cache pressure. - -.. include:: /includes/extracts/transactions-read-concern-majority-sharded-clusters.rst - -.. include:: /includes/extracts/transactions-read-concern-majority-replica-set.rst - -.. tip:: - - To check if read concern "majority" is disabled, You can run - :method:`db.serverStatus()` on the :binary:`~bin.mongod` instances - and check the :serverstatus:`storageEngine.supportsCommittedReads` - field. If ``false``, read concern "majority" is disabled. - -.. seealso:: - - - :option:`--enableMajorityReadConcern false ` - - - :setting:`replication.enableMajorityReadConcern: false - `. - .. _txns-locks: Acquiring Locks diff --git a/source/core/transactions-sharded-clusters.txt b/source/core/transactions-sharded-clusters.txt index 5f9f2753ae5..4be801aef84 100644 --- a/source/core/transactions-sharded-clusters.txt +++ b/source/core/transactions-sharded-clusters.txt @@ -113,27 +113,6 @@ Arbiters .. include:: /includes/extracts/transactions-arbiters.rst -.. |disabledrcmaj| replace:: :ref:`transactions-sharded-clusters-psa` - -.. _transactions-sharded-clusters-psa: - -Three Member Primary-Secondary-Arbiter Shards ---------------------------------------------- - -For a sharded cluster with three-member PSA shards, you may have -:ref:`disabled read concern "majority" ` -(i.e. :option:`--enableMajorityReadConcern false ` or -:setting:`replication.enableMajorityReadConcern: false -`) to avoid cache pressure. - -.. include:: /includes/extracts/transactions-read-concern-majority-sharded-clusters.rst - -To check if read concern "majority" is disabled, - You can run :method:`db.serverStatus()` and check the - :serverstatus:`storageEngine.supportsCommittedReads` field. If - ``false``, read concern "majority" is disabled. - Backups and Restores -------------------- diff --git a/source/core/transactions.txt b/source/core/transactions.txt index c1655accc6c..94696325a75 100644 --- a/source/core/transactions.txt +++ b/source/core/transactions.txt @@ -714,34 +714,6 @@ Arbiters .. include:: /includes/extracts/transactions-arbiters.rst -.. |disabledrcmaj| replace:: :ref:`transactions-disabled-rc-majority` - -.. _transactions-disabled-rc-majority: - -Disabled Read Concern Majority -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -A 3-member PSA (Primary-Secondary-Arbiter) replica set or a sharded -cluster with 3-member PSA shards may have disabled read concern -majority (:option:`--enableMajorityReadConcern false ` or -:setting:`replication.enableMajorityReadConcern: false -`) - -.. include:: /includes/extracts/transactions-read-concern-majority-sharded-clusters.rst - -.. include:: /includes/extracts/transactions-read-concern-majority-replica-set.rst - -.. tip:: - - To check if read concern "majority" is disabled, You can run - :method:`db.serverStatus()` on the :binary:`~bin.mongod` instances - and check the :serverstatus:`storageEngine.supportsCommittedReads` - field. If ``false``, read concern "majority" is disabled. - -For more information, see :ref:`transactions-psa` and -:ref:`transactions-sharded-clusters-psa`. - .. _transactions-wcmajority-disabled: Shard Configuration Restriction diff --git a/source/includes/extracts-transactions.yaml b/source/includes/extracts-transactions.yaml index db25827f8af..86e93717498 100644 --- a/source/includes/extracts-transactions.yaml +++ b/source/includes/extracts-transactions.yaml @@ -294,29 +294,6 @@ content: | # This is included in pages talking more about disabling rc majority and its effects. # Separate includes (see below) for transactions pages where the transactions leads as the subject ---- -ref: transactions-read-concern-majority-sharded-clusters -content: | - - On sharded clusters, - - If a transaction involves a shard that has :ref:`disabled read - concern "majority" `, you cannot - use read concern :readconcern:`"snapshot"` for the transaction. - You can only use read concern :readconcern:`"local"` or - :readconcern:`"majority"` for the transaction. If you use read - concern :readconcern:`"snapshot"`, the transaction errors and - aborts. - - .. code-block:: none - :copyable: false - - readConcern level 'snapshot' is not supported in sharded clusters when enableMajorityReadConcern=false. - - - Transactions whose write operations span multiple shards will - error and abort if any of the transaction's read or write - operations involves a shard that has disabled read concern - ``"majority"``. - --- ref: transactions-read-concern-majority-replica-set content: | @@ -459,8 +436,6 @@ content: | and abort if any transaction operation reads from or writes to a shard that contains an arbiter. - See also |disabledrcmaj| for transaction restrictions on shards that - have disabled read concern majority. --- ref: transactions-committed-visibility content: | diff --git a/source/includes/fact-eMRC-always-true-in-5.0.rst b/source/includes/fact-eMRC-always-true-in-5.0.rst new file mode 100644 index 00000000000..bf2fd75d3b1 --- /dev/null +++ b/source/includes/fact-eMRC-always-true-in-5.0.rst @@ -0,0 +1,11 @@ +Starting in MongoDB 5.0, +:setting:`~replication.enableMajorityReadConcern` and +:option:`--enableMajorityReadConcern` cannot be changed +and are always set to ``true`` due to storage engine improvements. + +In earlier versions of MongoDB, +:setting:`~replication.enableMajorityReadConcern` and +:option:`--enableMajorityReadConcern` are configurable and can be set +to ``false`` to prevent storage cache pressure from immobilizing a +deployment with a three-member primary-secondary-arbiter (PSA) +architecture. \ No newline at end of file diff --git a/source/includes/fact-enable-majority-readConcern.rst b/source/includes/fact-enable-majority-readConcern.rst deleted file mode 100644 index e09c76dee17..00000000000 --- a/source/includes/fact-enable-majority-readConcern.rst +++ /dev/null @@ -1,8 +0,0 @@ -To use :term:`read concern` level of :readconcern:`"majority"`, replica -sets must use :ref:`WiredTiger storage engine `. - -You can disable read concern :readconcern:`"majority"` for a deployment -with a three-member primary-secondary-arbiter (PSA) architecture; -however, this has implications for change streams (in MongoDB 4.0 and -earlier only) and transactions on sharded clusters. For more information, -see :ref:`disable-read-concern-majority`. diff --git a/source/reference/command/aggregate.txt b/source/reference/command/aggregate.txt index 8e08b3aba7c..d4d2ce83e50 100644 --- a/source/reference/command/aggregate.txt +++ b/source/reference/command/aggregate.txt @@ -546,8 +546,6 @@ majority of the nodes. .. important:: - - .. include:: /includes/fact-enable-majority-readConcern.rst - - .. include:: /includes/fact-aggregate-readConcern.rst - .. include:: /includes/fact-readConcern-most-recent-data-in-node.rst diff --git a/source/reference/command/count.txt b/source/reference/command/count.txt index f495203222b..d12937e375d 100644 --- a/source/reference/command/count.txt +++ b/source/reference/command/count.txt @@ -302,8 +302,6 @@ majority of the nodes. .. important:: - - .. include:: /includes/fact-enable-majority-readConcern.rst - - To use the ``readConcern`` level of ``"majority"``, you must specify a nonempty ``query`` condition. diff --git a/source/reference/command/distinct.txt b/source/reference/command/distinct.txt index fe8afae211a..fad176f1cac 100644 --- a/source/reference/command/distinct.txt +++ b/source/reference/command/distinct.txt @@ -298,9 +298,7 @@ majority of the nodes. .. note:: - - .. include:: /includes/fact-enable-majority-readConcern.rst - - - .. include:: /includes/fact-readConcern-most-recent-data-in-node.rst + .. include:: /includes/fact-readConcern-most-recent-data-in-node.rst .. code-block:: javascript diff --git a/source/reference/command/find.txt b/source/reference/command/find.txt index 2b72bf9dd5d..4148ebad8b1 100644 --- a/source/reference/command/find.txt +++ b/source/reference/command/find.txt @@ -583,8 +583,6 @@ The following operation on a replica set specifies a :term:`read concern` of :readconcern:`"majority"` to read the most recent copy of the data confirmed as having been written to a majority of the nodes. -.. include:: /includes/fact-enable-majority-readConcern.rst - .. code-block:: javascript db.runCommand( diff --git a/source/reference/command/geoSearch.txt b/source/reference/command/geoSearch.txt index 39e7c78905f..124dda47362 100644 --- a/source/reference/command/geoSearch.txt +++ b/source/reference/command/geoSearch.txt @@ -154,9 +154,7 @@ majority of the nodes. .. note:: - - .. include:: /includes/fact-enable-majority-readConcern.rst - - - .. include:: /includes/fact-readConcern-most-recent-data-in-node.rst + .. include:: /includes/fact-readConcern-most-recent-data-in-node.rst .. code-block:: javascript diff --git a/source/reference/configuration-options.txt b/source/reference/configuration-options.txt index 240ec5e8730..f8be3f8eee6 100644 --- a/source/reference/configuration-options.txt +++ b/source/reference/configuration-options.txt @@ -4138,32 +4138,12 @@ LDAP Parameters *Default*: true - - Starting in MongoDB 3.6, MongoDB enables support for - :readconcern:`"majority"` read concern by default. - - You can disable read concern :readconcern:`"majority"` to prevent - the storage cache pressure from immobilizing a deployment with a - three-member primary-secondary-arbiter (PSA) architecture. For more - information about disabling read concern :readconcern:`"majority"`, - see :ref:`disable-read-concern-majority`. - - To disable, set :setting:`replication.enableMajorityReadConcern` to false. :setting:`replication.enableMajorityReadConcern` has no effect for - MongoDB versions: 4.0.0, 4.0.1, 4.0.2, 3.6.0. - - .. important:: - - In general, avoid disabling :readconcern:`"majority"` read concern - unless necessary. However, if you have a three-member replica set - with a primary-secondary-arbiter (PSA) architecture or a sharded - cluster with a three-member PSA shards, disable to prevent the - storage cache pressure from immobilizing the deployment. - - .. include:: /includes/extracts/transactions-read-concern-majority.rst - - .. include:: /includes/fact-disable-majority-rc-rollbacks.rst - - .. include:: /includes/extracts/changestream-disable-rc-majority.rst + Configures support for :readconcern:`"majority"` read concern. + + Starting in MongoDB 5.0, + :setting:`~replication.enableMajorityReadConcern` cannot be changed + and is always set to ``true``. In earlier versions of MongoDB, + :setting:`~replication.enableMajorityReadConcern` was configurable. ``sharding`` Options diff --git a/source/reference/method/cursor.readConcern.txt b/source/reference/method/cursor.readConcern.txt index dae74a03284..e5c837940e5 100644 --- a/source/reference/method/cursor.readConcern.txt +++ b/source/reference/method/cursor.readConcern.txt @@ -60,11 +60,6 @@ Definition Considerations -------------- -``"majority"`` Read Concern -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -.. include:: /includes/fact-enable-majority-readConcern.rst - Read Your Own Writes ~~~~~~~~~~~~~~~~~~~~~ diff --git a/source/reference/method/db.collection.aggregate.txt b/source/reference/method/db.collection.aggregate.txt index fd5f2d11c28..e222c7ca864 100644 --- a/source/reference/method/db.collection.aggregate.txt +++ b/source/reference/method/db.collection.aggregate.txt @@ -552,8 +552,6 @@ majority of the nodes. .. note:: - - .. include:: /includes/fact-enable-majority-readConcern.rst - - .. include:: /includes/usage-read-concern-majority.rst - .. include:: /includes/fact-aggregate-readConcern.rst diff --git a/source/reference/method/db.collection.count.txt b/source/reference/method/db.collection.count.txt index 0589bd28ab2..2f5f147378a 100644 --- a/source/reference/method/db.collection.count.txt +++ b/source/reference/method/db.collection.count.txt @@ -132,8 +132,6 @@ Definition - Optional. Specifies the :term:`read concern`. The default level is :readconcern:`"local"`. - .. include:: /includes/fact-enable-majority-readConcern.rst - .. include:: /includes/usage-read-concern-majority.rst .. include:: /includes/fact-count-readConcern.rst diff --git a/source/reference/program/mongod.txt b/source/reference/program/mongod.txt index df345ebf037..c03ea4b9877 100644 --- a/source/reference/program/mongod.txt +++ b/source/reference/program/mongod.txt @@ -1836,33 +1836,12 @@ Replication Options *Default*: true - - Starting in MongoDB 3.6, MongoDB enables support for - :readconcern:`"majority"` read concern by default. - - You can disable read concern :readconcern:`"majority"` to prevent - the storage cache pressure from immobilizing a deployment with a - three-member primary-secondary-arbiter (PSA) architecture. For more - information about disabling read concern :readconcern:`"majority"`, - see :ref:`disable-read-concern-majority`. - - To disable, set :option:`--enableMajorityReadConcern` to false. :option:`--enableMajorityReadConcern` has no effect for - MongoDB versions: 4.0.0, 4.0.1, 4.0.2, 3.6.0. - - .. important:: - - In general, avoid disabling :readconcern:`"majority"` read concern - unless necessary. However, if you have a three-member replica set - with a primary-secondary-arbiter (PSA) architecture or a sharded - cluster with a three-member PSA shards, disable to prevent the - storage cache pressure from immobilizing the deployment. - - .. include:: /includes/extracts/transactions-read-concern-majority.rst - - .. include:: /includes/fact-disable-majority-rc-rollbacks.rst - - .. include:: /includes/extracts/changestream-disable-rc-majority.rst - + Configures support for :readconcern:`"majority"` read concern. + + Starting in MongoDB 5.0, + :option:`--enableMajorityReadConcern` cannot be changed + and is always set to ``true``. In earlier versions of MongoDB, + :option:`--enableMajorityReadConcern` was configurable. Sharded Cluster Options ~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/source/reference/read-concern-majority.txt b/source/reference/read-concern-majority.txt index c59696dfe35..ca9490fce53 100644 --- a/source/reference/read-concern-majority.txt +++ b/source/reference/read-concern-majority.txt @@ -42,12 +42,6 @@ Availability Read concern :readconcern:`"majority"` is available for use with or without causally consistent sessions and transactions. -You can disable read concern :readconcern:`"majority"` for a deployment -with a three-member primary-secondary-arbiter (PSA) architecture; -however, this has implications for change streams (in MongoDB 4.0 and -earlier only) and transactions on sharded clusters. For more -information, see :ref:`disable-read-concern-majority`. - Example ------- @@ -136,62 +130,11 @@ Read Your Own Writes .. include:: /includes/fact-read-own-writes.rst -.. _disable-read-concern-majority: +.. _disable-read-concern-majority: + +Disable Read Concern Majority +----------------------------- + +*For 3-Member Primary-Secondary-Arbiter Architecture* -Disable Read Concern Majority ------------------------------ - -*For 3-Member Primary-Secondary-Arbiter Architecture* - -You can disable read concern :readconcern:`"majority"` if you have a -three-member replica set with a primary-secondary-arbiter (PSA) -architecture or a sharded cluster with a three-member PSA shards. - -.. note:: - - If you are using a deployment other than a 3-member PSA, you do not - need to disable read concern majority. - -With a three-member PSA architecture, the cache pressure will increase -if any data bearing node is down. To prevent the storage cache pressure -from immobilizing a deployment with a PSA architecture, you can disable -read concern by setting either: - -- :option:`--enableMajorityReadConcern ` command line option to ``false``. - -- :setting:`replication.enableMajorityReadConcern` configuration file - setting to ``false``. - -To check if read concern "majority" is disabled, You can run -:method:`db.serverStatus()` on the :binary:`~bin.mongod` instances and -check the :serverstatus:`storageEngine.supportsCommittedReads` field. -If ``false``, read concern "majority" is disabled. - -.. important:: - - In general, avoid disabling :readconcern:`"majority"` read concern - unless necessary. However, if you have a three-member replica set - with a primary-secondary-arbiter (PSA) architecture or a sharded - cluster with a three-member PSA shard, disable to prevent the - storage cache pressure from immobilizing the deployment. - -.. note:: Change Streams - - .. include:: /includes/extracts/changestream-disable-rc-majority.rst - - -.. note:: Transactions - - .. include:: /includes/extracts/transactions-read-concern-majority.rst - -.. note:: Read Concern ``"snapshot"`` - - Disabling :readconcern:`"majority"` read concern affects read - operations on sharded clusters. - - .. include:: /includes/fact-readConcern-snapshot-disable-majority.rst - -.. note:: Rollback Considerations - - .. include:: /includes/fact-disable-majority-rc-rollbacks.rst +.. include:: /includes/fact-eMRC-always-true-in-5.0.rst diff --git a/source/reference/read-concern-snapshot.txt b/source/reference/read-concern-snapshot.txt index 903d253f147..c3339af51ed 100644 --- a/source/reference/read-concern-snapshot.txt +++ b/source/reference/read-concern-snapshot.txt @@ -41,10 +41,6 @@ the following read operations : All other read commands prohibit :readconcern:`"snapshot"`. -.. note:: - - .. include:: /includes/fact-readConcern-snapshot-disable-majority.rst - Operations ---------- @@ -64,15 +60,6 @@ Multi-document transactions support read concern individual operation level. To set the read concern for transactions, see :ref:`transactions-read-concern`. -For transactions on a sharded cluster, if any operation in the -transaction involves a shard that has :ref:`disabled read concern -"majority" `, you cannot use read -concern :readconcern:`"snapshot"` for the transaction. You can only use -read concern :readconcern:`"local"` or :readconcern:`"majority"` for -the transaction. If you use read concern :readconcern:`"snapshot"`, the -transaction errors and aborts. For more information, see -:ref:`transactions-disabled-rc-majority`. - .. _atClusterTime: Read Concern and ``atClusterTime`` diff --git a/source/reference/read-concern.txt b/source/reference/read-concern.txt index 23e3791f8ea..51cb171052e 100644 --- a/source/reference/read-concern.txt +++ b/source/reference/read-concern.txt @@ -100,16 +100,10 @@ The following read concern levels are available: :readconcern:`"majority"` is comparable in performance cost to other read concerns. - Availability: - - Read concern :readconcern:`"majority"` is available for use - with or without causally consistent sessions and transactions. - - - You can disable read concern :readconcern:`"majority"` for - a deployment with a three-member primary-secondary-arbiter - (PSA) architecture; however, this has implications for - change streams (in MongoDB 4.0 and earlier only) and - transactions on sharded clusters. For more information, see - :ref:`disable-read-concern-majority`. + **Availability:** + + Read concern :readconcern:`"majority"` is available for use with + or without causally consistent sessions and transactions. **Requirements:** To use :term:`read concern` level of :readconcern:`"majority"`, replica sets must use @@ -200,10 +194,6 @@ The following read concern levels are available: All other read operations prohibit :readconcern:`"snapshot"`. - .. important:: - - .. include:: /includes/fact-readConcern-snapshot-disable-majority.rst - .. include:: /includes/fact-readConcern-most-recent-data-in-node.rst diff --git a/source/release-notes/5.0-compatibility.txt b/source/release-notes/5.0-compatibility.txt index 67ad2f3a9df..1aa61bf1772 100644 --- a/source/release-notes/5.0-compatibility.txt +++ b/source/release-notes/5.0-compatibility.txt @@ -140,6 +140,11 @@ Shell packaging also changes in MongoDB v5.0. Refer to the Replica Sets ------------ +``enableMajorityReadConcern`` Is Not Configurable +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/fact-eMRC-always-true-in-5.0.rst + ``secondaryDelaySecs`` Configuration Setting ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/source/release-notes/5.0.txt b/source/release-notes/5.0.txt index 3413a419b90..a837f50577d 100644 --- a/source/release-notes/5.0.txt +++ b/source/release-notes/5.0.txt @@ -224,6 +224,11 @@ Starting in MongoDB 5.0, the :rsconf:`members[n]._id` field may be any integer value greater than or equal to ``0``. Previously, this value was limited to an integer between ``0`` and ``255`` inclusive. +``enableMajorityReadConcern`` Is Not Configurable +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. include:: /includes/fact-eMRC-always-true-in-5.0.rst + Enhanced Thread Pool Timeout Control ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/source/tutorial/add-replica-set-arbiter.txt b/source/tutorial/add-replica-set-arbiter.txt index 2043da39953..9f8daac059b 100644 --- a/source/tutorial/add-replica-set-arbiter.txt +++ b/source/tutorial/add-replica-set-arbiter.txt @@ -34,24 +34,6 @@ server or a monitoring host. Considerations -------------- -Read Concern ``majority`` and Three-Member PSA -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -.. warning:: For 3-Member Primary-Secondary-Arbiter Architecture - - - If you have a three-member replica set with a - primary-secondary-arbiter (PSA) architecture or a sharded cluster - with a three-member PSA shards, the cache pressure will increase if - any data bearing node is down and support for - :readconcern:`"majority"` read concern is enabled. - - To prevent the storage cache pressure from immobilizing a deployment - with a three-member primary-secondary-arbiter (PSA) architecture, - you can disable read concern "majority" starting in MongoDB 4.0.3 - (and 3.6.1+). For more information, see - :ref:`disable-read-concern-majority`. - Replica Set Protocol Version ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/source/tutorial/upgrade-revision.txt b/source/tutorial/upgrade-revision.txt index 12f9f3a424a..b0168194db9 100644 --- a/source/tutorial/upgrade-revision.txt +++ b/source/tutorial/upgrade-revision.txt @@ -68,24 +68,6 @@ token when connected to a member that has not been updated (i.e. only accepts ``v0`` or BinData token) and fail. In such cases, the client must wait for the upgrade to complete before resuming change streams. -3-Member PSA Architecture -~~~~~~~~~~~~~~~~~~~~~~~~~ - -Starting in MongoDB 3.6, MongoDB enables support for -:readconcern:`"majority"` read concern by default. - -You can disable read concern :readconcern:`"majority"` to prevent -the storage cache pressure from immobilizing a deployment with a -primary-secondary-arbiter (PSA) architecture. However, - -- .. include:: /includes/extracts/changestream-disable-rc-majority.rst - -- .. include:: /includes/fact-disable-majority-rc-rollbacks.rst - -- .. include:: /includes/extracts/transactions-read-concern-majority.rst - -For more information, see :ref:`disable-read-concern-majority`. - Staging Environment Check ~~~~~~~~~~~~~~~~~~~~~~~~~~