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

Balancer should not try to clone data if a shard is in forced draining mode

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

      When a shard is put into forced draining mode, the balancer should schedule any chunks on this shard to be moved off of it. Since the shard is completely down, we cannot actually move any data over so we should skip the clone phase of the migration and just execute the metadata update on the config server.

            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: