-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
-
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).
- duplicates
-
SERVER-80974 Unclean shutdown while dropping local.* collection and indexes can make the catalog inconsistent
- Closed
- is related to
-
SERVER-79245 Unclean shutdown while dropping collection and indexes to resync can make the catalog inconsistent
- Closed