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

Call _setStableTimestampForStorage() after updating lastApplied and lastDurable

    • Replication
    • Repl 2024-03-04

      call _setStableTimestampForStorage() even in j:true cases since lastApplied and lastDurable will be updated independently. 

      we can do something optimization to avoid always calling _setStableTimestampForStorage, such as only call it when old lastApplied < lastCommitted, we probably should also feature flag gate it.

       

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            kishore.devireddy@mongodb.com Kishore Devireddy
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: