[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: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 4 weeks ago | ||||
| Story Points: | 0.25 | ||||
| Description |
|
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: |
| Comment by Githook User [ 18/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 18/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |