-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.19, 6.0.15, 7.0.7, 7.3.0-rc5
-
Component/s: None
-
Catalog and Routing
-
ALL
-
CAR Team 2024-04-01, CAR Team 2024-04-15
-
2
createIndex may end up creating an "orphaned" bucket collection (with default empty collection options) when executed concurrently with dropCollection.
- Create a timeseries collection
- Create index starts (translates view ns to bucket ns)
- Drop collection starts
- Drop collection succeeds
- Create index continues (timeseries not existing anymore)
- Create index implicitly creates the bucket collection
- Create index succeeds
Reproducible attached (including diff to apply on ae89abf235 to add a failpoint during create index).
As part of this ticket we should be able to add `createIndex` to create_all_type_collections.js concurrency test
- is related to
-
SERVER-96211 Investigate how a `system.buckets` collection can be created without timeseries options
- Closed
-
SERVER-99290 Invalid timeseries buckets collections prevent completion of FCV 8.0 upgrade
- Closed
-
SERVER-99345 Prevent sharding/moving a time-series buckets collection without the 'timeseries' options on FCV 8.0+
- Closed
- related to
-
SERVER-79630 Disallow creating and preventing upgrading with system.buckets namespaces which aren't timeseries collections
- Closed
-
SERVER-97488 Race condition with collation and time series can yield incorrect query results
- Closed