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

Do not timestamp applyOps writes on standalones

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.3, 3.7.1
    • Component/s: Replication, Storage
    • Labels:
      None

      Description

      We put in a back-door here so that we could unittest timestamps. It says that non-master-slave, non-replicated applyOps writes are timestamped with their provided timestamps. This means that standalone applyOps writes will get timestamped with the provided timestamps. If the provided timestamps are out of order (which is almost certain), that will cause a problem.

        Attachments

          Activity

            People

            Assignee:
            judah.schvimer Judah Schvimer
            Reporter:
            judah.schvimer Judah Schvimer
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: