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

XMLWordPrintableJSON

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

      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 (Inactive)
              Reporter:
              Daniel Gottlieb (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: