When a storage transaction to update an index to multikey is aborted, it is possible for the in-memory state of an index to appear as multikey but the durable state to remain as non-multikey.
In this scenario, the IndexCatalogEntryImpl (erroneous in-memory state) may contain path-level information which lead to this optimization being erroneously applied to subsequent multikey writes and leaving the index as non-multikey in the catalog.
- is related to
-
SERVER-41766 Secondary may encounter prepare conflict when applying write that sets the multikey flag
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-57127 Refactor multikey and other state out of IndexCatalogEntry
-
- Closed
-
-
SERVER-53675 Allow validate to fix up multikey metadata
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-