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

Unclean shutdown after untimestamped collection drop can make catalog inconsistent.

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Catalog and Routing
    • ALL
    • Hide

      (Description to be filled)

      Show
      (Description to be filled)
    • Execution EMEA Team 2023-10-02
    • 144

      In our codebase, unclean node shutdowns after untimestamped collection drops can cause catalog inconsistencies (* idents known to _mdb_catalog but not to storage*), leading to node crashes on restart. This issue, observed in shard merge, is a general problem found in various areas of our codebase(see also SERVER-75740 which does untimestamped drop of system.profile collection).

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: