[SERVER-47572] Snapshot reads without atClusterTime should read from majority committed snapshot Created: 15/Apr/20  Updated: 29/Oct/23  Resolved: 27/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: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-47569 Allow operations with readConcern sna... Closed
is depended on by SERVER-47573 Update readConcern to include the atC... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-05-04
Participants:

 Description   

For snapshot reads without “atClusterTime”, set timestamp readSource to the timestamp of the current majority committed snapshot.
Similar to WiredTigerRecoveryUnit::obtainMajorityCommittedSnapshot and getMinSnapshotForNextCommittedRead, we need to select a majority committed snapshot to read at and then setTimestampReadSource to kProvided with the selected timestamp.



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

Author:

{'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}

Message: SERVER-47572 Snapshot reads use majority committed timestamp
Branch: master
https://github.com/mongodb/mongo/commit/2f7abf486d3fc0f785cef1df949ae7fb80c8ba58

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