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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 4.0.0
    • 4.0.1
    • Storage
    • Fully Compatible
    • ALL
    • Storage NYC 2018-07-30
    • 0

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35000 A RecoveryUnit::ReadSource of "no timestamp" should be distinguishable from the default of kNone

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: