[SERVER-47576] Include atClusterTime in cursor responses for snapshot reads Created: 15/Apr/20  Updated: 29/Oct/23  Resolved: 28/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-47573 Update readConcern to include the atC... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-05-04
Participants:

 Description   

When a server receives a read command with read concern level "snapshot" outside of a transaction, it replies with a new field, atClusterTime, representing the timestamp of the read. This timestamp is guaranteed to be majority committed.

{cursor: {..., atClusterTime: <Timestamp>}, ...}

The reply has the same format if the request included afterClusterTime or not.



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

Author:

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

Message: SERVER-47576 Test secondary snapshot reads
Branch: master
https://github.com/mongodb/mongo/commit/52a73692175cad37f942ff5e6f3d70aacbbb113d

Comment by Githook User [ 28/Apr/20 ]

Author:

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

Message: SERVER-47576 Include atClusterTime in snapshot read reply
Branch: master
https://github.com/mongodb/mongo/commit/846cd7c189350edffecfe260e149571927d19d95

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