[DOCS-9357] Update documentation related to 'forcing a replica set member to be primary' Created: 21/Nov/16  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Nishant Bhardwaj Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

The documentation should be updated to point out that the method of forcing a replica set member to be primary has long-term consequences that are not readily apparent to someone who came to that particular page from a google search for something force Mongo primary. While it is clear in the Adjust Priority for Replica Set Member documentation, what those numbers actually mean, those replica set priority numbers seem to be used without context in the Force a Member to be Primary by Setting its Priority High of 'Force a Member to Become Primary'.

The alternative procedure Force a Member to be Primary Using Database Commands of 'Force a Member to Become Primary' does not depend on changing member priorities so should be recommended over the first procedure.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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