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

Do not choose only first shard of all shards associated with a zone when pre-splitting during shard collection

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.3, 4.3.3, 4.0.15
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.2, v4.0
    • Sharding 2019-12-16

      Currently, when pre-splitting a collection during shardCollection using existing zones, we choose the first shard associated with the zone to place a chunk on. This can cause a problem if there are many shards associated with the same zone - the balancer will still schedule migrations to balance the zones afterward.

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: