Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-80136

Create a new command to change the DBPrimary without moving any collections

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 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.

            allison.easton@mongodb.com Allison Easton
            allison.easton@mongodb.com Allison Easton
            0 Vote for this issue
            2 Start watching this issue