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

Primary shard not distributed

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.2
    • Component/s: Sharding, WiredTiger
    • None
    • ALL
    • Sharding 2017-02-13

      Hi team,

      Mongodb configuration :

      • Version: 3.4.2
      • 20 shards : 1 primary / 1 secondary / 1 arbiter
      • Engine : Wiredtiger
      • 3 configs
      • 3 mongos

      New dbs created on the cluster are allocated on the same shard.
      More than 100 dbs have been created (mostly contains only a collection with an index), primary shard is the same. We tried to put some data on few DBs (as allocation algorithm is based on the number of db by shard + their size), but new database still goes on the same place.
      We didn't find any relevant thing in conf or logs that could explain or help us to debug.

      Is there a specific setting to set ? Or is it an (known) issue ?

      Thank you,
      Anthony

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            anthony@sendinblue.com Anthony Brodard
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: