[DOCS-7738] Fix Replica Set Majority Determination Created: 25/Apr/16 Updated: 03/Nov/17 Resolved: 14/Sep/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: | Andre Spiegel | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.cloud.mongodb.com/tutorial/edit-replica-set/#remove-a-replica-set-member |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 6 years, 22 weeks ago | ||||
| Epic Link: | DOCSP-252 | ||||
| Story Points: | 0.5 | ||||
| Description |
|
When removing a member of a replica set, this page says that you need to retain a majority of the members of the original replica set. That sentence is wrong or misleading, since after removing a member, you have a new "original replica set", and you need a majority of that replica set to maintain writability. |
| Comments |
| Comment by Anthony Sansone (Inactive) [ 14/Sep/17 ] |
|
The related ticket (MMS-3809) is not on any release plan. Closing this ticket until such time as MMS-3809 is assigned and resolved. |
| Comment by Anthony Sansone (Inactive) [ 14/Sep/17 ] |
|
No potential action timeline. |