[DRIVERS-1729] Investigate changes in PM-1970: Change the Default Read Concern to Always Be Local Created: 05/May/21  Updated: 27/May/22  Resolved: 10/May/21

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Driver Changes: Needed
Server Compat: 5.0

 Description   
Downstream Change Summary

The current read concern default for sharded secondary reads (that are not associated with a causally consistent session) is 'available' and in all other cases is 'local'. Starting in 5.0, we plan to change the default read concern to always be 'local'.

Description of Linked Ticket

Epic Summary

Summary

Review the current read and write concern settings and propose changes to provide more intuitive and safe defaults.

Motivation

There are two primary motivations for adjusting our defaults. First, although MongoDB allows users to choose the right tradeoff between performance and consistency, the nuances of the system are complex and are often misused, or surprising to users. We should provide more intuitive and stronger consistency default settings out of the box. Second, MongoDB has battled with the user perception that it is not reliable or intentionally chooses unsafe defaults to appear faster in benchmarks. By changing the defaults, we eliminate that argument.

Cast of Characters

  • Product Owner:
  • Project Lead:
  • Program Manager:
  • Drivers Contact:

Documentation

Scope Document
Technical Design Document
Product Description



 Comments   
Comment by Esha Bhargava [ 10/May/21 ]

No driver changes needed.

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