-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-02-16
-
200
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
Currently, the idempotency check logic of create commands is conditional on the viewless timeseries feature flag. This means that if a concurrent FCV transition happens, we could execute the wrong idempotency check based on a stale value of the viewless timeseries feature flag.
For instance, the following scenario could happen:
- viewless feature flag is DISABLED
- legacy timeseries collection already exists
- attempt to create a legacy timeseries collections with same options of the already existsing one. We found the already existing collection and we throw NamespaceExists
- FCV downgrade happen and the viewless collection gets upgraded to viewfull
- perform idempotency checks based on value of feature flag at 1.. Thus we look for the presence of the system.buckets legacy timeseries namespace, but since the collection got upgraded we won't find it. Thus, we wrongly bubble up NamespaceExists error.
- fixes
-
SERVER-82072 Time-series collection creation does not perform shard version checks on buckets collection
-
- Closed
-
- is related to
-
SERVER-82072 Time-series collection creation does not perform shard version checks on buckets collection
-
- Closed
-