Unclean shutdown after untimestamped collection drop can make catalog inconsistent.

XMLWordPrintableJSON

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

      (Description to be filled)

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

      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
              Reporter:
              Suganthi Mani
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: