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

manually set oplog visibility on rollback start

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.0-rc0
    • Replication, Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-05-21

    Description

      The timestamp that oplog reads use for proper visibility is a global value that is set asynchronously. Currently, it is possible for rollback to do reads on the oplog as part of its work, and such reads may be subject to stale oplog visibility. SERVER-34091 is one example of this. To ensure no other problems are lurking, we should set the oplog visibility timestamp synchronously when rollback starts.

      Attachments

        Issue Links

          Activity

            People

              louis.williams@mongodb.com Louis Williams
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: