[DOCS-1407] The order of config servers can be changed, but only if all servers are restarted Created: 17/Apr/13  Updated: 04/Sep/13  Resolved: 15/Aug/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Ed Costello Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-1393 Migrate three config servers Closed
Participants:
Days since reply: 10 years, 44 weeks ago

 Description   

Based on note & i/m exchange with scotthernandez:

  • 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


Generated at Thu Feb 08 07:40:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.