[DOCS-748] Config server order must remain constant Created: 13/Nov/12  Updated: 13/Nov/12  Resolved: 13/Nov/12

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

Type: Improvement Priority: Major - P3
Reporter: Tyler Brock Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 11 years, 14 weeks, 1 day ago

 Description   

In the mongos docs (http://docs.mongodb.org/manual/reference/mongos/) we should add a note that says:

"However, once the config server order is initialized (used) it cannot be changed without restarting the whole cluster."

after this section:

"Each mongos reads from the first config server in the list provided. If your configuration databases reside in more that one data center, you should specify the closest config servers as the first servers in the list."



 Comments   
Comment by auto [ 13/Nov/12 ]

Author:

{u'date': u'2012-11-13T17:45:44Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-748: clarification about configdb ordering
Branch: master
https://github.com/mongodb/docs/commit/49353e9a65a6c9dcc01029a96566dfb8a8f0fcfd

Comment by Sam Kleinman (Inactive) [ 13/Nov/12 ]

We don't want to have:

mongos --configdb db1.example.net,db2.example.net,db3.example.net

and

mongos --configdb db3.example.net,db2.example.net,db1.example.net

In the same cluster...

In that case I think it makes sense to remove the idea that the mongos should specify the config server that's closest, because in a big cluster that's always going to indicate a different order...

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