Don't create the first collection chunk on a primary drained shard

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.3, 3.7.2
    • Affects Version/s: 3.2.17, 3.4.10, 3.6.2
    • Component/s: None
    • Fully Compatible
    • v3.6
    • Sharding 2018-02-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Once we mark a primary shard to drain via

      db.runCommand( { removeShard: "my_primary_shard"})
      

      the first chunk for new sharded collections will still be created on the primary drained shard and then it will be moved to another shard automatically.

      We should be able to avoid this step and directly create the first chunk on another shard.

            Assignee:
            Janna Golden
            Reporter:
            Renato Riccio
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: