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

Ensure insert into new collection is replicated before asserting in initial_sync_drop_against_last_stable.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.4.3
    • Fix Version/s: 4.4.4
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2021-01-25
    • Linked BF Score:
      16

      Description

      Currently, as part of initial_sync_drop_against_last_stable.js, we drop a collection and then create a new one with the same name. We also insert a document into the new collection and check that it exists once initial sync is complete. Currently, there is a race that the document is not covered by initial sync (the optime for the insert is > than the stopOptime for initial sync), and we fail the assertion that the inserted document exists after initial sync is complete.

        Attachments

          Activity

            People

            Assignee:
            jason.chan Jason Chan
            Reporter:
            jason.chan Jason Chan
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: