Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42921

writeConcernMajorityJournalDefault warnings should be logged with Warning Level Severity

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
    • Replication
    • v4.2, v4.0, v3.6

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: