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

system.indexes 3.4 to 3.6 upgrade semantics on wiredTiger may cause mongod 4.0 to fail to start up

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.0.0-rc0
    • None
    • Upgrade/Downgrade
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-05-07
    • 0

    Description

      system.indexes does not receive a UUID upon setFCV from 3.4 to 3.6 regardless of storage engine. Mongod 4.0 only exempts system.indexes from the UUID startup check if the storage engine is MMAP. This means that if a user creates system.indexes on mongod 3.4 or earlier when using wiredTiger, upgrades to mongod 3.6, then upgrades to mongod 4.0, mongod 4.0 will fail to startup.

      One solution to avoid this issue is to drop system.indexes on startup if it fails the UUID check.

      Attachments

        Activity

          People

            maria.vankeulen@mongodb.com Maria van Keulen
            maria.vankeulen@mongodb.com Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: