[DOCS-14791] [SERVER] Transactions documentation report incorrect default write concern for MongoDB 5.0 Created: 13/Sep/21 Updated: 13/Nov/23 Resolved: 04/Nov/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0, 5.1.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adam Harrison | Assignee: | Jason Price |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 2 years, 13 weeks, 6 days ago |
| Epic Link: | DOCSP-15042 |
| Story Points: | 3 |
| Description |
|
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) |
| Comments |
| Comment by Githook User [ 04/Nov/21 ] |
|
Author: {'name': 'jason-price-mongodb', 'email': '69260375+jason-price-mongodb@users.noreply.github.com', 'username': 'jason-price-mongodb'}Message: Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> |
| Comment by Githook User [ 04/Nov/21 ] |
|
Author: {'name': 'jason-price-mongodb', 'email': '69260375+jason-price-mongodb@users.noreply.github.com', 'username': 'jason-price-mongodb'}Message: Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> |