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

Improve oplog truncation thread's log level 0 logging

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.9.0
    • Storage
    • Fully Compatible
    • ALL
    • Execution Team 2021-02-08
    • 123

    Description

      The log message that always show up for oplog truncation, which can indicate when oplog truncation is taking a long time (high resource consumption, perhaps), with log-level 1 is:

      "WiredTiger record store oplog truncation finished in: <elapsedMillis>ms"

      A more informative message for debugging, which communicates an oplog size guess, might be the log-level 1 prior message:

      "Finished truncating the oplog, it now contains approximately <sizeInfo_numRecords_load> records totaling to <sizeInfo_dataSize_load> bytes"

      Or, better yet, we could combine them into one message at log-level 0.

      Attachments

        Activity

          People

            bynn.lee@mongodb.com Bynn Lee
            dianna.hohensee@mongodb.com Dianna Hohensee
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: