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

listIndexes shouldn't include in-progress background index builds on primary nodes

    • Storage Execution
    • Fully Compatible
    • ALL
    • v3.6, v3.4
    • Storage 2017-12-04
    • 0

      Currently listIndexes includes in-progress background indexes that haven't been committed yet. This can theoretically (I haven't tested it) lead to an inconsistency in initial sync in the following scenario:

      1. Start bg index on primary
      2. Start initial sync
      3. Initial sync runs listIndexes and builds all returned indexes
      4. Initial sync finishes with the bg index
      5. Kill the bg index build on primary (or have it fail due to a recent insert)

      I think after these steps, the secondary will have an index that the primary doesn't.

            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            mathias@mongodb.com Mathias Stearn
            0 Vote for this issue
            15 Start watching this issue