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

Shard can be removed while an ongoing migration is happening

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 2019-10-07, Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16
    • 13

      Setup:

      • ShardA has no chunks/collections/database

      Scenario:
      1. Chunk migration from ShardZ to ShardA starts.
      2. RemoveShard for ShardA starts.
      3. Remove shards sees that there's no database/chunk for ShardA so proceeds to removing shard.
      4. Chunk is now sent to ShardA after it has been "removed".

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: