-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0, 7.0.0, 8.0.0-rc0
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
v8.0, v7.3, v7.0, v6.0, v5.0
-
CAR Team 2024-05-13
-
2
SERVER-41766 introduced a side transaction to commit multikey metadata changes immediately and independently of the parent multi-document transaction to avoid a corner case resulting in an infinite prepare conflict.
However, wildcard indexes maintain the multikey metadata paths inside the index table itself, which is different from other indexes which maintain them inside the catalog table, and the code neglects to wrap wildcard multikey paths maintenance inside the side transaction, making wildcard multikey setting vulnerable to infinite prepare conflicts.
- is related to
-
SERVER-41766 Secondary may encounter prepare conflict when applying write that sets the multikey flag
- Closed
-
SERVER-59842 Setting wildcard index as multikey can cause prepare conflicts
- Closed