mongos does bad things when adding replica sets with same name as shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.1.0
    • Affects Version/s: 2.0.1
    • Component/s: Replication, Sharding
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If you add a shard with a name of a replica set which already exists as a shard (and has a different name), the addShard command returns false and no new shard is added, but the existing shard's replica set is strangely replaced by the failing addShard's host.

      Should also make sure our other handling of shard vs. replica set names is sane.

        1. mongos_weird_names.js
          1.0 kB
          Greg Studer

            Assignee:
            Spencer Brody (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: