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

Unique index that gets rebuilt as part of startup recovery/repair is using data format version as 6 or 8 and NOT 11 or 12.

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.4, 4.3.4
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Execution Team 2020-01-27
    • 44

      Unique index rebuilt as part of mongodb 4.2 startup repair/recovery will  have either kDataFormatV2KeyStringV1IndexVersionV2 (8) or kDataFormatV1KeyStringV0IndexVersionV1 (6) since FCV is uninitialized at that point of time.  To be noted, we initialize FCV only after rebuilding the index which is over here. As a result, we break the assumption mentioned here. Also, if we upgrade/restart the node with mongodb binary version 4.3+, we would crash the server as part of startup index sanity check (Sanity check got introduced only from mongodb 4.3+).

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: