The WiredTiger metadata file can be logically inconsistent (for example, there can be a table entry where there's a missing underlying file entry).
Deal with this in two ways:
(1) if the metadata is inconsistent when reading with a metadata:create cursor, treat it as missing; and
(2) use a single transaction for create and drop operations so the metadata is not left inconsistent by a crash.
- is related to
-
WT-3964 Stop wrapping schema operations in a transaction
-
- Closed
-
- related to
-
SERVER-32453 WTKVEngine::getAllIdents mishandles cursor->next return code.
-
- Closed
-
-
WT-4225 Automate a backup test that simulates volume snapshot via dd
-
- Closed
-
-
-
- Backlog
-