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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.0.0
    • Fix Version/s: 4.0.1
    • Component/s: Storage
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Storage NYC 2018-07-30
    • Linked BF Score:
      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

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

                Dates

                Created:
                Updated:
                Resolved: