Snapshot time may advance before fetching a command's operationTime

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • ALL
    • Repl 2026-03-16, Repl 2026-03-30
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For majority reads, the operationTime uses replCoord->getCurrentCommittedSnapshotOpTime(). That time may advance on a different thread, leading to operationTime being reported as larger than it was at the time of the read. Would the recoveryUnit's getPointInTimeReadTimestamp() be more correct?

            Assignee:
            Brad Cater
            Reporter:
            Brad Cater
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: