-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
CAR Team 2026-04-27
-
200
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-96916 enforced stricter checks in establishConsistentCollection, assuming the commit pending entry always represents what the storage transaction will commit.
However, this is currently not true for multikey index builds committing. And it is possible that CRUD multikeyness changes may also need some work.
The issue with index build commit is that it reuses the same CRUD path which sets multikeyness in an onCommit hook. For the commit case this should not be necessary, as the collection MODE_X lock is held.Â
- is related to
-
SERVER-96916 CollectionCatalog::establishConsistentCollection does not check commit pending entries with a read timestamp
-
- Closed
-