-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
Repl 2019-06-17, Repl 2019-07-01
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.
- is depended on by
-
SERVER-34881 Don't wait for writeConcern when committing a read-only transaction with readConcern: 'local'
- Backlog
- is related to
-
SERVER-34880 Make readConcern:local wait for write concern on a read-only transaction
- Closed
- related to
-
SERVER-40123 Transaction diagnostics should not report upconverted readConcern
- Closed
-
SERVER-38906 Multi-document transactions should not perform timestamped read ahead of all-committed
- Closed