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

Error if removeShard command run with forceRemoveByAbandoningData for a shard that is the only shard associated with a zone

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

      Currently if a shard is in draining mode but is the only shard in a particular zone, the balancer will just skip this chunk and the command will never return "completed". If removeShard is run with the the forceRemoveByAbandoningData option, we should fail the command in this case and inform the user they must add a new shard to this zone. We cannot add a shard to this zone automatically due to various restrictions (i.e. GDPR), and it is unacceptable in this case for the shard to remain in forcedDraining mode.

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