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

Implement initial drain policy for unsharded collections when the user specifies a destination shard

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2024-01-22

      When `draining` and `userSpecifiedDestination` are true, the unsharded balancer policy should generate migrations to move collections off of the draining shard and to `destinationShard`.

      This will require adding `userSpecifiedDestination` and `destinationShard` to the cluster statistics. The collections currently located on the draining shard can be fetched from config.collections/config.chunks in this initial implementation. This information can be fetched from the unsharded policy's cache later on, but this initial implementation will allow testing to start for removeShard.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: