-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 9.0.0-rc0
-
Component/s: Catalog
-
None
-
Catalog and Routing
-
ALL
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
Since SERVER-106887 it is possible to rename timeseries collections in viewless format, both in a single DB and across DB.
This makes them vulnerable to the race in SERVER-118421: Because of the catalog scanning pattern, a viewless timeseries undergoing rename across DBs may be missed by setFCV downgrade.
This is splitting from that ticket because:
- Viewless timeseries upgrade/downgrade has custom catalog scanning logic.
- It may be preferable to simply disallow viewless timeseries renames if the feature flag is disabled (i.e. during kDowngrading).
- is related to
-
SERVER-118421 Catalog changes during setFCV can race with rename across DBs
-
- Closed
-
-
SERVER-123220 Collectionless $listClusterCatalog may miss collections being renamed across DBs
-
- Needs Scheduling
-
-
SERVER-123292 Remove code to disallow rename viewless timeseries across DBs while downgrading to viewful timeseries
-
- Backlog
-
-
SERVER-106887 Support rename of viewless timeseries collections
-
- Closed
-