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

Allow ExceededMemoryLimit to be a benign log warning instead of an invariant in the JournalFlusher

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Execution Team 2021-12-13
    • 35

      The jstestfuzzer provoked a WT cache full error on the in-memory engine. This should only be an issue for the in-memory engine – the durable engine should be in a panic evicting mode before this could happen. The server invariants on the error here in the JournalFlusher

      We should log the warning and continue – the journal flusher runs periodically and would repeatedly log the error message, and cmds waiting for j:true would return the error message.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: