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

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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.17, 3.4.10, 3.6.2
    • Fix Version/s: 3.6.3, 3.7.2
    • Component/s: None
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2018-02-12

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              janna.golden Janna Golden
              Reporter:
              renato.riccio Renato Riccio
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: