-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Labels:None
The "Transactions and Write Concern" Section of the Transactions documentation say the following:
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 w: 1. See also Default MongoDB Read Concerns/Write Concerns.
This is incorrect as of MongoDB 5.0.
The linked documentation for this section (Default MongoDB Read Concerns/Write Concerns) shows that the default write concern as of MongoDB 5.0 is `w: "majority"` (with special considerations for arbiters)