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

Reduce the initial minimum number of chunks to 1 per shard for empty collections with hashed shard key

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • Fully Compatible
    • Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Following the removal of the auto-splitter in versions >= v6.0.3, balancing does not happen anymore on number of chunks but on actual data size and the balancer is issuing moveRange commands (DOCS-15363) to atomically split+move subparts of a chunk.

      Purpose of this ticket is to change the default behavior for creating/distributing chunks when sharding an empty collection with hashed shard key: one chunk per shard, in line with the decision taken also for resharding (SERVER-68050).

            Assignee:
            robert.sander@mongodb.com Robert Sander
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: