Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-83278

Update snapshot read's returned operationTime to be the timestamp of the snapshot

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability
    • Cluster Scalability 2024-2-5, Cluster Scalability 2024-2-19
    • 2

    Description

      Based on this code, when we return the operation time of a read operation, if the read concern was majority, we return the CurrentCommittedSnapshotOpTime, while if the read concern was anything else (local, linearizable, or snapshot), we returned the lastApplied optime.

      For snapshot reads, is this the intended behavior/contract for operationTIme?
      We do additionally attach an atClusterTime field in cursor responses. Should the operationTime also be the `atClusterTime`, or is it ok to keep it as the lastApplied?

      Attachments

        Activity

          People

            wenqin.ye@mongodb.com Wenqin Ye
            huayu.ouyang@mongodb.com Huayu Ouyang
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: