[DOCS-9230] Comment on: "manual/tutorial/adjust-replica-set-member-priority.txt" Created: 28/Oct/16  Updated: 30/Oct/23

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

Type: Bug Priority: Minor - P4
Reporter: Docs Collector User (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Won't Do Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.com/v3.0/tutorial/adjust-replica-set-member-priority/
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Referrer: https://docs.mongodb.com/manual/tutorial/adjust-replica-set-member-priority/
Screen Resolution: 1920 x 1080


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

 Description   

Would like to see a comment/statement that tells us that these configuration changes persist across reboots.

Also, the settings shown in the example imply that node 1 is a low-priority node for assuming the primary role where as nodes 2 and 3 will battle for primary.

In practice, wouldn't the converse be true? You'd want to ensure that one of the default nodes is favored to be the primary...so that node would be assigned a value higher than the others implying that you want that node to be the primary and you really don't care which of the others becomes a replacement primary.



 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:57:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.