oplog reads on secondaries should read at lastApplied timestamp

XMLWordPrintableJSON

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

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

              Assignee:
              Eric Milkie
              Reporter:
              Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: