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

removeShard command run with forceRemoveByAbandoningData should move the db primary for any dbs whose primary is the shard to be removed

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The removeShard does not run movePrimary for any databases whose primary is the shard being removed currently. When run with the new option "forceRemoveByAbandoningData", the command should run movePrimary for the dbs and avoid the need for any user manual intervention.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: