[SERVER-80136] Create a new command to change the DBPrimary without moving any collections Created: 16/Aug/23  Updated: 06/Dec/23  Resolved: 06/Dec/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-83925 movePrimary coordinator should stop c... In Progress
is depended on by SERVER-1334 Have 'removeshard' move out databases... Backlog
Assigned Teams:
Catalog and Routing
Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 06/Dec/23 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-80136 Create a new command to change the DBPrimary without moving any collections

GitOrigin-RevId: 016bb1fdf66b1a98d2871c61581465d39dbf9b25
Branch: master
https://github.com/mongodb/mongo/commit/b61d95fd87161d3fdeec6b0c95856ade4aa8b0f6

Generated at Thu Feb 08 06:42:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.