[DOCS-14381] Investigate changes in SERVER-55701: Ignore replica set config's getLastErrorDefaults Created: 26/Apr/21  Updated: 13/Nov/23  Resolved: 26/Aug/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.0.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ian Fogelman
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-55701 Ignore replica set config's getLastEr... Closed
Duplicate
is duplicated by DOCS-14440 Investigate changes in SERVER-56241: ... Closed
Participants:
Days since reply: 2 years, 23 weeks, 6 days ago
Epic Link: DOCSP-15042
Story Points: 0

 Description   

Description

Downstream Change Summary

We are ignoring the settings.getLastErrorDefaults field now, and should tell users to use the cluster wide write concern instead

Description of Linked Ticket

null

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Ian Fogelman [ 26/Aug/21 ]

This issue is covered in DOCS-14440 and is currently in copy review status.

 

DOCS-14440 Verbatim :

 
We do not allow setting settings.getLastErrorDefaults in the config to a customized value, i.e anything other than:

 

{w: 1, wtimeout: 0{color:#000000}}
 

 

on startup/reconfig

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