Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-1407

The order of config servers can be changed, but only if all servers are restarted

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Last comment by Customer:
      true

      Description

      Based on note & i/m exchange with Scott Hernandez:

      • The configdb option (order of the config servers) is not fixed forever, only for a running cluster
        • All mongos must use the same configdb option (same order)
        • The first (avail) config server listed is used for reads
      • The configdb option (with the order) can be changed, but only if all mongos (and shards) are brought down and then up with a new configdb string.
      • Only mongos and the shards keep track of this setting
        • The actual config servers know nothing about the order, or each other

      http://docs.mongodb.org/manual/reference/mongos/?highlight=configdb#cmdoption-mongos--configdb

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bgrabar Bob Grabar
              Reporter:
              epc Ed Costello
              Participants:
              Last commenter:
              Jonathan Dahl Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                8 years, 29 weeks ago
                Date of 1st Reply: