[DOCS-9262] Ensuring Replica Set Settings from Old to New Replica Sets Created: 01/Nov/16 Updated: 06/Mar/17 Resolved: 06/Mar/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | post-launch_mongodb-3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.opsmanager.mongodb.com/current/tutorial/restore-replica-set/ |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 15 weeks, 1 day ago | ||||||||
| Epic Link: | DOCSP-252 | ||||||||
| Description |
|
This page needs to talk about recording the settings in the old replica set config and restoring them into the new one. We are also now discouraging the use of rs.initiate() with no parameters. Instead, we should encourage passing the new replica set config to the initiate() helper. |
| Comments |
| Comment by Allison Reinheimer Moore [ 01/Nov/16 ] |
|
tony.sansone To you for grooming, good sir. |