[SERVER-47569] Allow operations with readConcern snapshot outside of transactions (mongod) Created: 15/Apr/20  Updated: 29/Oct/23  Resolved: 20/Apr/20

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-47571 Wait for majority committed snapshot ... Closed
is depended on by SERVER-47572 Snapshot reads without atClusterTime ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-05-04
Participants:

 Description   

Remove this uassert to allow “snapshot” reads outside of transactions.



 Comments   
Comment by Githook User [ 20/Apr/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-47569: Allow readConcern snapshot outside of transactions (mongod)
Branch: master
https://github.com/mongodb/mongo/commit/e9c00e8abdef460c7174b329288f9e7a1c4d7f86

Comment by Lingzhi Deng [ 20/Apr/20 ]

mongos has this uassert in strategy.cpp.

Comment by A. Jesse Jiryu Davis [ 20/Apr/20 ]

It looks like we don't need an equivalent ticket in mongos; service_entry_point_mongos.cpp doesn't have this uassert. I guess mongos relies on mongod to enforce the current rule, "prohibit snapshot reads outside transactions".

Generated at Thu Feb 08 05:14:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.