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

addShard should report back an error when adding a new shard with the same replica set name as an existing shard

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.2.0-rc0
    • None
    • Fully Compatible
    • Sharding 2022-09-19, Sharding 2022-10-03
    • 3

    Description

      Currently if we add a new shard with the same replica set name and configuration as an existing shard, addShard does not report that as an error and does a no-op. To give a better user experience, we should give users some indication that an existing shard with the same name/config is already part of the cluster.

      Attachments

        Activity

          People

            nandini.bhartiya@mongodb.com Nandini Bhartiya
            jason.zhang@mongodb.com Jason Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: