-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11
In 8.0, we will be deprecating movePrimary by turning it into a noop that logs a warning to use moveCollection to move data rather than movePrimary. The balancer will be updated to drain unsharded collections as well as sharded ones. But we will still need a ddl operation to commit the change of database primary at the end of the draining phase.
This ticket is to introduce a new command that will move only user system collections (which are untracked and so cannot be moved by the balancer) and then update the databasePrimary shard metadata.
- is depended on by
-
SERVER-83925 movePrimary coordinator should stop cloning unsplittable collections
- Closed
-
SERVER-1334 Have 'removeshard' move out databases automatically as well
- Backlog