-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-05-21
A transaction started with readConcern:local that doesn't do any writes does not need to wait for the data it read to be committed when the transaction commits. SERVER-34038 implemented the behavior that causes read-only txns with RC 'majority' and 'snapshot' to wait for the data read to be committed at commit time, and intentionally excluded RC 'local' from that waiting. However, since SERVER-34837 isn't going to get done for 4.0, we should temporarily make RC 'local' behave like RC 'majority' and 'snapshot' in this case, so that the fact that the readConcern default is incorrect will not be observable.
- related to
-
SERVER-34837 Make the default readConcern level for transactions be speculative majority
- Backlog
-
SERVER-34881 Don't wait for writeConcern when committing a read-only transaction with readConcern: 'local'
- Backlog
-
SERVER-34038 Make sure that commitTransaction waits for writeConcern after a read-only transaction
- Closed