-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
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.
- duplicates
-
SERVER-80974 Unclean shutdown while dropping local.* collection and indexes can make the catalog inconsistent
- Closed
- is related to
-
SERVER-81879 startupRecoveryForRestore can drop tables whose catalog write is not yet checkpointed
- Closed
- related to
-
SERVER-80974 Unclean shutdown while dropping local.* collection and indexes can make the catalog inconsistent
- Closed
-
SERVER-81355 Unclean shutdown after untimestamped collection drop can make catalog inconsistent.
- Closed