-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 6.0.0, 6.1.0, 6.3.0, 6.2.0-rc6, 7.1.0
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
ALL
-
v7.0, v6.0
-
Execution Team 2024-04-29, Execution Team 2024-05-13
We started supporting `gCollModIndexUnique` from 6.0. Between versions 6.0 and 7.1, there's a possibility that we check the feature flag 'gCollModIndexUnique' during startup here before the FCV is initialized. This caused an invariant failure, preventing the server from restarting. That problematic check is unnecessary as it verifies if the index option 'prepareUnique' read from disk on startup is still compatible with FCV. We already have a safeguard in place that prevents downgrades from 6.0 to succeed if any collection has an index with the 'prepareUnique' field set.
- is related to
-
SERVER-71068 Partial indexes should not check FCV during startup
- Closed
- related to
-
SERVER-91738 [v6.0] CreateIndex command should check if featureFlagCollModIndexUnique is enabled when the indexOptions contain prepareUnique.
- Needs Merge
-
SERVER-87375 Audit the collection and index code for potentially unsafe FCV checks during startup.
- Open