-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
v8.0, v7.3, v7.0
-
CAR Team 2024-08-05
The resharding, moveCollection and unshardCollection commands on the router are calling into the primary shard by using executeCommandAgainstDatabasePrimary that attaches UNSHARDED placement version by default.
Even though the attached version was not correct, this was fine until today because it was not being checked on the shard side. However, SERVER-92896 is soon going to add a check for timeseries in the command handler causing a version check (if present). Because of that, we should rely on executeDDLCoordinatorCommandAgainstDatabasePrimary that only attaches the database version.
- is depended on by
-
SERVER-92896 Incorrect queries on timeseries with extended range on non dbPrimary (root cause not fixed - disabled resharding for timeseries so the bug can't occurr on moved unsharded collections)
- Closed
- related to
-
SERVER-93115 Review the use executeCommandAgainstDatabasePrimary helper for DDL commands
- Closed