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

FCV should be initialized before attempting to restart in-progress index builds

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Index Maintenance
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2020-07-27
    • 6

      When a mongod restarts and attempts to rebuild its unfinished indexes, it does so before the FCV version has been initialized. When the in-progress index specs are validated, therefore, the index comparison defaults to the FCV 4.4 behaviour and does not distinguish the indexes based on their differing partialFilterExpressions. This will cause an fassert if any conflicting indexes exist.

      Similar issues have occurred before; see e.g. SERVER-45374. After speaking with louis.williams and daniel.gottlieb, the consensus is that the proper solution would be to ensure that the FCV is always initialized before attempting any index validation.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            bernard.gorman@mongodb.com Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: