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

Wrong description of all_durable timestamp in repl architecture guide

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Repl 2023-12-25, Repl 2024-01-08, Repl 2024-01-22

      all_durable: All transactions with timestamps earlier than the all_durable timestamp are committed. This is the point at which the oplog has no gaps, which are created when we reserve timestamps before executing the associated write. Since this timestamp is used to maintain the oplog visibility point, it is important that all operations up to and including this timestamp are committed and durable on disk. This is so that we can replicate the oplog without any gaps. 

      The "and durable on disk" should be removed.

      URL: https://docs.devprod.prod.corp.mongodb.com/mongo/src/mongo/db/repl/

            Assignee:
            m.maher@mongodb.com Moustafa Maher
            Reporter:
            daotang.yang@mongodb.com Daotang Yang
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: