[DOCS-4923] Expand from 1 config server to 3 config servers doesn't mention the mongos command-line change Created: 05/Mar/15  Updated: 09/Feb/18  Resolved: 18/Jan/18

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v3.0

Type: Improvement Priority: Major - P3
Reporter: Andrew Ryder (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: bite-sized, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 6 years, 4 weeks ago
Story Points: 0.25

 Description   

RE: http://docs.mongodb.org/manual/tutorial/deploy-config-servers/#deploy-three-config-servers-for-production-deployments

This is a really great guide to expanding from one config server to three config servers for the purposes of deploying an existing system into production. It mentions the use of the existing command-line for the config servers, but omits the necessary command-line change of all mongos to include all three config servers - if they are restarted as the instructions say, then the cluster will continue to use just one config server. I believe this should be covered in step 4.



 Comments   
Comment by Githook User [ 18/Jan/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-4923: config servers 1 to 3
Branch: v2.4
https://github.com/mongodb/docs/commit/600c56ebcb06cb84efbaac6dce7c534af765a6fa

Comment by Githook User [ 18/Jan/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-4923: config servers 1 to 3
Branch: v2.6
https://github.com/mongodb/docs/commit/ba3e4c224dabe7eb796a96d8d2f41089f69270fe

Comment by Githook User [ 18/Jan/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-4923: config servers 1 to 3
Branch: v3.0
https://github.com/mongodb/docs/commit/090d4d87a48bfe38f64504eaac672646c3fdd078

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