DOCS-13628 write concern and transactions (#406) (#470)

* DOCS-13628 write concern and transactions

* DOCS-13628 write concern and transactions

* DOCS-13628 write concern and transactions

* DOCS-13628 write concern and transactions

* DOCS-13628 write concern and transactions

* DOCS-13628 write concern and transactions

* DOCS-13628-write-concern-and-transactions

* DOCS-13628-write-concern-and-transactions

* DOCS-13628-write-concern-and-transactions

* DOCS-13628-write-concern-and-transactions

Co-authored-by: jason-price-mongodb <[email protected]>

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/core/transactions.txt

@@ -706,6 +706,8 @@ values, including:
 
    .. include:: /includes/return-commit-decision-parameter.rst
 
+   .. include:: /includes/write-concern-majority-and-transactions.rst
+
 General Information
 -------------------
 

source/includes/write-concern-majority-and-transactions.rst

@@ -0,0 +1,8 @@
+If you specify a :writeconcern:`"majority"` write concern for a
+:doc:`multi-document transaction </core/transactions>` and the
+transaction fails to replicate to the :ref:`calculated majority
+<calculating-majority-count>` of :term:`replica set` members, then the
+transaction may not immediately roll back on replica set members.
+The replica set will be :term:`eventually consistent <eventual
+consistency>`. A transaction is always applied or rolled back on all
+replica set members.

source/reference/write-concern.txt

@@ -16,7 +16,6 @@ Write Concern
    :class: singlecol
 
 
-
 Write concern describes the level of acknowledgment requested from
 MongoDB for write operations to a standalone :binary:`~bin.mongod` or
 to :doc:`replica sets </replication>` or to :doc:`sharded clusters
@@ -30,6 +29,8 @@ pass the write concern on to the shards.
    operation level`. Do not explicitly set the write concern for
    individual write operations in a transaction.
 
+   .. include:: /includes/write-concern-majority-and-transactions.rst
+
 Starting in MongoDB 4.4, replica sets and sharded clusters support
 setting a global default write concern. Operations which do not 
 specify an explicit write concern inherit the global default 
@@ -107,6 +108,8 @@ available:
        client can read the result of that write with a
        :readconcern:`"majority"` readConcern.
 
+       .. include:: /includes/write-concern-majority-and-transactions.rst
+
        See :ref:`wc-ack-behavior` for when :binary:`~bin.mongod` instances
        acknowledge the write.