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

Less strict configdb checking for config repl set

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.9
    • Affects Version/s: 3.1.7
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 9 (09/18/15)

      Currently, the setShardVersion command includes the configdb field which contains the connection string to the config server of the current cluster. If the shard is already aware of the config server, then it will compare the configdb field with it's own. This is currently done with a string comparison so it can fail if one of them is missing a member in the list even they are both referring to the same set.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: