Skip to content

DOCS-14791 default write concern #6079

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 4, 2021
Merged

DOCS-14791 default write concern #6079

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 13 additions & 5 deletions source/core/transactions.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -643,11 +643,19 @@ You can set the transaction-level :doc:`write concern
concern for the commit.

- If the transaction-level write concern and the session-level write
concern are unset, transaction-level write concern defaults to the
client-level write concern. By default, client-level write concern is
:writeconcern:`w: 1 <\<number\>>`. See also
:doc:`/reference/mongodb-defaults`.

concern are unset, the transaction-level write concern defaults to the
client-level write concern of:

- :writeconcern:`w: "majority" <"majority">` in MongoDB 5.0 and later,
with differences for deployments containing :ref:`arbiters
<replica-set-arbiter-configuration>`. See
:ref:`wc-default-behavior`.

- :writeconcern:`w: 1 <\<number\>>` in MongoDB 4.4 and earlier.

.. seealso::

:doc:`/reference/mongodb-defaults`

Transactions support all write concern :ref:`w <wc-w>`
values, including:
Expand Down