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

Run listIndexes with a single snapshot during initial sync

    • ALL
    • Execution Team 2019-12-02, Execution Team 2019-12-16

      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.

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

              Created:
              Updated:
              Resolved: