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

Make timestamp behavior consistent across read sources in the recovery unit

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Storage Execution

    Description

      The different read sources establish its readAt timestamp in different ways in the RecoveryUnit.

      kProvided and kLastApplied sets the timestamp when setTimestampReadSource is called.

      kNoOverlap, kAllDurableSnapshot, kMajorityCommitted opens a snapshot if not already opened and sets the timestamp when calling getPointInTimeReadTimestamp.

      The different behavior around when a timestamp is set and which calls will open a snapshot makes it difficult to use the API in a correct way that will work in a consistent way for the different read sources. We should try and unify the behavior.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: