[SERVER-54411] Communicate change of default write concern via docs/marketing Created: 09/Feb/21  Updated: 22/Jul/21  Resolved: 22/Jul/21

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

Type: Task Priority: Major - P3
Reporter: Gaurav Kumar (Inactive) Assignee: Gaurav Kumar (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

We propose to change the default write concern for our clusters to w:majority. We will need to communicate this change as part of 5.0 release, and probably in advance of the 5.0 release.

This change may be communicated via Atlas UI, ops manager, and/or marketing and documentation.



 Comments   
Comment by Gaurav Kumar (Inactive) [ 22/Jul/21 ]

Mainly change related to documentation and marketing activities. No downstream changes.

Comment by Gaurav Kumar (Inactive) [ 22/Jul/21 ]

We have finished the following activities:

Blog on w:majority - https://www.mongodb.com/blog/post/default-majority-write-concern-providing-stronger-durability-guarantees-out-box
.live talk on read write concern - https://www.youtube.com/watch?v=J5P31wJUbgI
Document changes for w:majority change

In light of this accomplished work, we can close this ticket.

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