[SERVER-45597] Deprecation warning when applying a ReplSetConfig with getLastErrorDefaults other than { w: 1, wtimeout: 0 } Created: 16/Jan/20  Updated: 29/Oct/23  Resolved: 06/Feb/20

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

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-13394 Investigate changes in SERVER-45597: ... Closed
Related
related to DOCS-13186 Deprecate getLastErrorDefaults Closed
Backwards Compatibility: Minor Change
Sprint: Sharding 2020-01-27, Sharding 2020-02-10
Participants:

 Description   

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).



 Comments   
Comment by Githook User [ 06/Feb/20 ]

Author:

{'username': 'devkev', 'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com'}

Message: SERVER-45597 deprecation startup warning when applying replset config with custom getLastErrorDefaults
Branch: master
https://github.com/mongodb/mongo/commit/58081d16653b6aa0befbf9eeef68efcce890f6cc

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