[SERVER-42921] writeConcernMajorityJournalDefault warnings should be logged with Warning Level Severity Created: 20/Aug/19  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Assigned Teams:
Replication
Backport Requested:
v4.2, v4.0, v3.6
Participants:

 Description   

Right now, we log two messages to warn users about writeConcernMajorityJournalDefault interacting with --nojournal and the in memory storage engine.

They are currently not logged with Warning Level Severity, so they are undetectable for users running log watchers. In addition, they are logged to "startup warnings" ramlog, but not during startup.


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