[DOCS-2533] Restore a sharded cluster procedure does not instruct to start config servers Created: 14/Jan/14 Updated: 22/Jan/14 Resolved: 22/Jan/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 4 weeks ago | ||||
| Description |
|
At http://docs.mongodb.org/manual/tutorial/restore-sharded-cluster/ step 2.a has instructions to start the three config servers, but step 2 is only used if the hostnames of the nodes has changed. If step 2 is not used, then the process would read to:
Which would start the mongos nodes without the config server running, and will fail. Need to include a line (potentially another step) indicating to start the config servers (if not already done) prior to step 3. |
| Comments |
| Comment by Githook User [ 22/Jan/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 22/Jan/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |