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

oplog reads on secondaries should read at lastApplied timestamp

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.6
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-04-23
    • 50

      Currently, oplog reads use the oplog visiblity timestamp, but this value is not maintained properly while a batch is being applied.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: