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

Do not allow different ShardId vs. Replica Set Id

    XMLWordPrintableJSON

Details

    • Sharding

    Description

      In most cases MongoDB defaults the shard Id to be the same as the Replica Set Id. Ops Manager does not allow users to import a cluster that has shard Ids that are inconsistent replica set Ids.

      However it appears there are certain cases where these can be changed, or where the customer can change manually. It seems the correct resolution is not to patch in Ops Manager, but to resolve at the source and not allow this to occur in the server.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            jordan.sumerlus Jordan Sumerlus
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: