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

Stable timestamp can be set to timestamp not in oplog

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.6.7, 4.0.0-rc0
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Repl 2018-05-21
    • 15

    Description

      We set the stable timestamp using the "candidates" list which is populated whenever we move "lastApplied" forward. On primaries, we set lastApplied to the "all committed timestamp", which is not necessarily a timestamp in the oplog. On primaries we need to actually add the operation commit time to the candidates list, rather than the "all committed timestamp".

      Attachments

        Activity

          People

            judah.schvimer@mongodb.com Judah Schvimer
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: