[DOCS-7314] Documentation is not clear on the implications of removing multiple instances to reduce the size of a RS Created: 01/Mar/16  Updated: 11/Jan/17  Resolved: 16/Mar/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Brian Blevins Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MMS-Cloud-Automation - mongod 3.0.9 with mmapv1 on CentOS.


Issue Links:
Related
Participants:
Days since reply: 7 years, 50 weeks, 1 day ago

 Description   

Feedback from customer on CS ticket indicates the documentation fails to mention that you should not remove multiple members from a RS simultaneously. The RS may have too few voting members and the primary may step down.

https://jira.mongodb.org/browse/CS-28572

From the customer:

That documentation is not clear on the implications of removing multiple instances to reduce the size of a RS. I would suggest updating the documentation to make it clear that removing multiple members of an RS must either be done one node at a time, or that you should not remove more that would allow the original RS to form a majority.

The documentation in question is:

https://docs.cloud.mongodb.com/tutorial/edit-replica-set/
Refer to the section "Remove a Replica Set Member" near the bottom of the page.


Generated at Thu Feb 08 07:54:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.