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

Unclean shutdown while dropping collection and indexes to resync can make the catalog inconsistent

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Catalog and Routing
    • ALL
    • Execution EMEA Team 2023-09-18, Execution EMEA Team 2023-10-02

      Initial sync will drop all tables in all replicated databases without a timestamp before resyncing. This means that the drop pending ident reaper will immediately drop the table in WT the next time it runs. The table drops in WT are non-transactional and cannot be rolled back. This leads to immediately dropping the table in WT even if the catalog changes are not stable/checkpointed. As a result, during startup recovery, the table no longer exists in WT but continues to exist in the catalog. The server tries to query the index table metadata from WT but WT likely returns ENOENT and we crash.

            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            0 Vote for this issue
            11 Start watching this issue