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

Ignore "cannot index parallel arrays" errors during initial sync because they are transient

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.0.12, 3.2.7, 3.3.9
    • 3.3.10
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 17 (07/15/16)

    Description

      During initial sync, there is a race between when we create our indexes and when we insert documents with multiple arrays. Consider the following order of events (possible in find_dedup.js):

      1. Secondary starts fetching operations from primary for its oplog buffer
      2. Primary creates a compound index on two fields a and b
      3. Primary drops the collection
      4. Primary inserts document

      {a: [1,2,3], b: [4,5,6]}

      5. Secondary copies the collection, including document

      {a: [1,2,3], b: [4,5,6]}

      , but not including the compound index on fields a and b.
      6. Secondary starts to apply its oplog
      7. Secondary creates a compound index on fields a and b
      8. Secondary gets a "cannot index parallel arrays" error.

      Later on the secondary will drop this collection and reinsert

      {a: [1,2,3], b: [4,5,6]}

      and get to a consistent state if it is allowed to continue.

      Attachments

        Issue Links

          Activity

            People

              judah.schvimer@mongodb.com Judah Schvimer
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: