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

`multiInitialSyncApply` should consider setting a read timestamp of `kNoTimestamp`

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.1
    • Affects Version/s: 4.0.0
    • Component/s: Storage
    • Fully Compatible
    • ALL
    • Storage NYC 2018-07-30
    • 0

      When SERVER-35000 was committed to master, the only oplog application method was multiSyncApply. However on 4.0, there was also multiInitialSyncApply. I believe this part of the patch is also intended to be applied to multiInitialSyncApply.

            Assignee:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: