[DOCS-6246] Comment on: "manual/core/replica-set-priority-0-member.txt" Created: 21/Sep/15  Updated: 30/Oct/23  Due: 26/Jan/23  Resolved: 26/Jan/23

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

Type: Bug Priority: Critical - P2
Reporter: Asya Kamsky Assignee: Alison Huh
Resolution: Done Votes: 0
Labels: bite-sized, ready-for-work, reopened
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/manual/core/replica-set-priority-0-member/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36
Referrer: http://docs.mongodb.org/manual/core/replica-set-elections/
Screen Resolution: 1680 x 1050
repo: docs
source: core/replica-set-priority-0-member


Issue Links:
Gantt End to End
has to be finished together with DOCS-5341 Comment on: "manual/core/replica-set-... Closed
Participants:
Days since reply: 1 year, 1 week, 6 days ago
Epic Link: DOCSP-26173
Story Points: 0.25

 Description   

As of SERVER-14403 write concern majority means majority of voting replica set members.

We should audit the docs to fix-up any examples that imply otherwise (since pre-3.0 all members were used for WC majority calculation.



 Comments   
Comment by Alison Huh [ 26/Jan/23 ]

PR: https://github.com/10gen/docs-mongodb-internal/pull/2442

Comment by Sarah Olson [ 31/Oct/22 ]

Topic: voting replica set voting nodes.

Want to fix examples here. Many examples also in driver docs. 

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