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

Have internal findAndModifyImageLookup set the synthetic oplog entry to timestamp of findAndModify - 1

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.3, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • v5.0
    • Repl 2021-07-26, Repl 2021-08-09

      With SERVER-58740, we should be able to guarantee that there will be no collisions when setting the forged no-op image oplog entry timestamp to be the TS of the findAndModify - 1.

            Assignee:
            jason.chan@mongodb.com Jason Chan
            Reporter:
            jason.chan@mongodb.com Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: