[SERVER-34837] Make the default readConcern level for transactions be speculative majority Created: 03/May/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-34881 Don't wait for writeConcern when comm... Backlog
Related
related to SERVER-40123 Transaction diagnostics should not re... Closed
related to SERVER-38906 Multi-document transactions should no... Closed
is related to SERVER-34880 Make readConcern:local wait for write... Closed
Assigned Teams:
Replication
Sprint: Repl 2019-06-17, Repl 2019-07-01
Participants:

 Description   

If the readConcern field is omitted when starting a transaction, the transaction is supposed to default to readConcern 'speculative majority'.  Currently they default to 'local'.  There is no difference in behavior between those two in 4.0, but over time their behavior is likely to diverge, for example by SERVER-34881.


Generated at Thu Feb 08 04:38:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.