[DOCS-9299] Extend replica set best practice (Comment on: "mms/tutorial/edit-replica-set.txt") Created: 10/Nov/16 Updated: 03/Nov/17 Resolved: 25/Aug/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | post-launch_mongodb-3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vick Mena (Inactive) | 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/edit-replica-set/ |
||
| Attachments: |
|
| Participants: | |
| Days since reply: | 6 years, 24 weeks, 2 days ago |
| Epic Link: | DOCSP-252 |
| Story Points: | 0.2 |
| Description |
|
A best practice for adding a new node to an existing replica set involves dragging and dropping the process to the new node before hitting "Review & Deploy." That is not captured in this document and it would be useful to have that spelled out as it's not exactly intuitive. |
| Comments |
| Comment by Githook User [ 28/Aug/17 ] |
|
Author: {'username': 'atsansone', 'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com'}Message: ( |
| Comment by Githook User [ 28/Aug/17 ] |
|
Author: {'username': 'atsansone', 'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com'}Message: ( |