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

Handle missing index idents during startup recovery even if we're not a standalone.

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • ALL
    • Execution Team 2022-09-05, Execution Team 2022-09-19, Execution Team 2022-10-03
    • 5

      Similar to SERVER-63865, replica set nodes can fail to startup after an unclean shutdown if we didn't finish an index build (two phase).

      After a node crashes during an index build, we can startup and have the correct catalog entry but not have the corresponding index table. During index build recovery, we check that the collection is initialized. This code path leads us to initialize the index catalog and eventually we try to access the index table.

      We likely need to generalize the solution in SERVER-63865 to apply to nodes in startup recovery in general, regardless of whether they are standalone nodes, to prevent opening index tables that may not exist.

            gregory.wlodarek@mongodb.com Gregory Wlodarek
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            0 Vote for this issue
            7 Start watching this issue