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

Fix ShardId override issue during database creation

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1

      When creating a new database, we let the user send a request like adminCommand({enableSharding: 'config', primaryShard: 'regularShardId'}) but then override the shardId for the db's primary shard to config. 

      We should use the same model as in regular databases and throw an error notifying the database is already created in a different primary shard, if the user-selected shard is not config.

            Assignee:
            Unassigned Unassigned
            Reporter:
            pau.baldillou-salse@mongodb.com Pau Baldillou Salse (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: