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

Improve primary shard selection

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 1

      Currently the engine will select as primary shard for a new db the most empty shard (code).

       

      For an empty cluster usually the dbs are created all together and therefore all dbs will be located on the same shard.
      The selection algorithm could be improved in order to distribute the primary shards even when the cluster is empty, something like:

      • take the smallest shard
      • take all the shards in the smallest + threashold (e.g. 50GB)
      • from them chose the one with lowest number of collections
      • if all the same chose one random

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            renato.riccio@mongodb.com Renato Riccio
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: