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

Run listIndexes with a single snapshot during initial sync

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • None
    • None
    • Catalog, Index Maintenance, Replication
    • None
    • ALL
    • Execution Team 2019-12-02, Execution Team 2019-12-16

    Description

      Without this we can get idempotency problems during initial sync. We can try to create two indexes during collection cloning that never existed simultaneously in real life. Eventually we will get a dropIndex oplog entry for one of the two, but at collection clone time we don't know which one so we can't just drop one to fix the idempotency violation.

      This was hypothesized while I talked with milkie regarding SERVER-27122.

      Attachments

        Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-33946 Decrease number of initial sync attempts in tests to 1

          • Major - P3 - Major loss of function.
          • Blocked
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-27122 Restart initial sync for known index idempotency errors; fail for unknown ones.

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

          Activity

            People

              milkie@mongodb.com Eric Milkie
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: