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

ShardCollection should not create chunks on a draining shard

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • Hide

      Repro attached in files, should fail when running in the sharding suite.

      Show
      Repro attached in files, should fail when running in the sharding suite.

      SERVER-65666 addressed this problem by making it so that the initial split policy will not choose draining shards when creating initial chunks. However, the create collection coordinator creates the initial chunks before actually committing them on the config server.

      This means that there is still a case in which shardCollection will create chunks on a draining shard if removeShard is called after the initial chunks are created.

      As part of this ticket, we should investigate whether this is additionally a problem with resharding. Resharding using the initial split policies to choose the new chunks for the collection, so it is possible that there is a similar problem here if the initial chunks are created and then a shard is removed before persisting those chunks.

        1. remove_shard_shard_collection_repro.diff
          6 kB

            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:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: