[DOCS-13394] Investigate changes in SERVER-45597: Deprecation warning when applying a ReplSetConfig with getLastErrorDefaults other than { w: 1, wtimeout: 0 } Created: 06/Feb/20  Updated: 13/Nov/23  Resolved: 13/Jul/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.4, 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: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-45597 Deprecation warning when applying a R... Closed
Duplicate
is duplicated by DOCS-13186 Deprecate getLastErrorDefaults Closed
Participants:
Days since reply: 3 years, 30 weeks, 2 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

For Cloud, if Cloud/Ops Manager supports customisation of getLastErrorDefaults in replica set configurations, then it will eventually need to migrate to Cluster-Wide Write Concern Defaults instead, as getLastErrorDefaults is being deprecated.

For Docs, the deprecation of getLastErrorDefaults itself needs to be documented, see DOCS-13186. Possibly also this deprecation startup warning might also need to be documented.

Description of Linked Ticket

Note this is not to change the validity of such configs, so the warning should not occur during validation, only when the config is actually applied by the node as being the current active replset config (regardless of whether it has come from local.system.replset during startup initialisation, or the replSetReconfig command, or a heartbeat). It should also not occur when getLastErrorDefaults are consulted to be applied to an operation (this would cause significant log spam).

Could be warning() or startupWarning(). startupWarning() has the advantage of better visibility (eg. shows up in the shell and Cloud/Ops Manager), but at the cost of not being able to be cleared except via a mongod restart (SERVER-19790).

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 13/Jul/20 ]

Author:

{'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}

Message: (DOCS-13394): Deprecate getLastErrorDefaults custom values
Branch: master
https://github.com/mongodb/docs/commit/33b9ffc9e6f6b89a25de3c8ffdc4b3de37bbc259

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