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

prepareUnique index option FCV compatibility check shouldn't be performed during startup

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.11, 6.0.17
    • Affects Version/s: 6.0.0, 6.1.0, 6.3.0, 6.2.0-rc6, 7.1.0
    • Component/s: None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v7.0, v6.0
    • Execution Team 2024-04-29, Execution Team 2024-05-13

      We started supporting `gCollModIndexUnique` from 6.0. Between versions 6.0 and 7.1, there's a possibility that we check the feature flag 'gCollModIndexUnique' during startup here before the FCV is initialized. This caused an invariant failure, preventing the server from restarting. That problematic check is unnecessary as it verifies if the index option 'prepareUnique' read from disk on startup is still compatible with FCV. We already have a safeguard in place that prevents downgrades from 6.0 to succeed if any collection has an index with the 'prepareUnique' field set.

        1. HELP-56516.repro.js
          1 kB
          Suganthi Mani

            Assignee:
            gavin.peters@mongodb.com Gavin Peters (Inactive)
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: