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

Initial sync may fail with IndexOptionsConflict when applying stale startIndexBuild oplog entry

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0, 6.0.17
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v6.0
    • Execution Team 2023-03-06
    • 2

      Initial sync may fail with IndexOptionsConflict when applying stale startIndexBuild oplog entry if the stale (i.e. dropped) index has the same spec as a more up-to-date index under a different name.

      More specifically, let's say the primary creates {a: 1} with name "a1", drops it, then re-creates the same index with name "a2", and initial sync clones "a2" but later needs to re-apply createIndex of "a1". In this case, initial sync would fail with IndexOptionsConflict when applying "a1".

      SERVER-47164 added code to handle name conflicts during initial sync but it doesn't handle spec conflicts (under different index name).

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: