-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Labels:None
Description
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.)
- documents
-
SERVER-45597 Deprecation warning when applying a ReplSetConfig with getLastErrorDefaults other than { w: 1, wtimeout: 0 }
-
- Closed
-
- is duplicated by
-
-
- Closed
-