[DOCS-11971] Main readConcernpage makes no mention of new default in 3.6 Created: 16/Aug/18  Updated: 29/Oct/23  Resolved: 05/Nov/18

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 3.6

Type: Bug Priority: Major - P3
Reporter: Eric Sommer Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 5 years, 22 weeks, 6 days ago
Epic Link: DOCSP-1769
Story Points: 0.2

 Description   

----------------------------

Original Description

Read concern documented here: https://docs.mongodb.com/v3.6/reference/read-concern/

On this page it says:
.bq Starting in MongoDB 3.6, "majority" read concern is always enabled, and this setting has no effect.

But the first page has no mention that "majority" is automatically enabled for replica sets starting in 3.6.
----------------------------

Description

Bring the main read concern reference page into consistency with the read concern configuration option page.

Scope of changes (files that need work and how much)

https://docs.mongodb.com/v3.6/reference/read-concern/

Needs a mention of the fact that as of v3.6 read concern is always "majority".

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Githook User [ 06/Sep/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11971: add sentence about readconcernmajority enabled by default in read concern landing page
Branch: v3.6
https://github.com/mongodb/docs/commit/94a183d74cdb192f1770c48ce7496765848abacf

Generated at Thu Feb 08 08:04:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.