[SERVER-34880] Make readConcern:local wait for write concern on a read-only transaction Created: 07/May/18  Updated: 29/Oct/23  Resolved: 09/May/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-11690 Docs for SERVER-34880: Make readConce... Closed
Related
related to SERVER-34837 Make the default readConcern level fo... Backlog
related to SERVER-34881 Don't wait for writeConcern when comm... Backlog
related to SERVER-34038 Make sure that commitTransaction wait... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-05-21
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 09/May/18 ]

Author:

{'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto', 'username': 'mtrussotto'}

Message: SERVER-34880 Make readConcern:local wait for write concern on a read-only transaction
Branch: master
https://github.com/mongodb/mongo/commit/4d0e6ee525d0a1372994b258358eef515a420240

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