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

Start tracking timestamps on both primary and secondary using the oplog visibility manager

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Repl 2024-08-05, Repl 2024-08-19, Repl 2024-09-02

      Primary: track timestamps on transaction opTime reservation and untrack on transaction commit/rollback, mostly the changes are in LocalOplogInfo::getNextOpTimes.

      Secondary: anywhere we call oplogDiskLocRegister (during steady state, initial sync, etc) with {{orderedCommit }} set to true, excluding in unit tests.

            Assignee:
            Unassigned Unassigned
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: