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

Journal flusher's persistent session causes WT to log warning

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc2
    • None
    • None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2023-05-15, Execution Team 2023-05-29

    Description

      Running the server for an hour, when idle, will log the following warning:

      {"t":{"$date":"2023-03-01T10:53:37.015+00:00"},"s":"W",  "c":"WT",       "id":22430,   "ctx":"thread29","msg":"WiredTiger message","attr":{"message":{"ts_sec":1677668017,"ts_usec":15090,"thread":"5836:0x7fa4acd38700","session_name":"sweep-server","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"WARNING","verbose_level_id":-2,"msg":"Session 13 (@: 0x0x55f142d9fae8 name: EMPTY) did not run a sweep for 60 minutes."}}}
      

      With some GDB investigation, I discovered that this is the always-active session we use to flush the journal , and it is never reset for the lifetime of the server. As is noted in SERVER-31912, this does not cause problems because we never open cursors using this session.

      WT-10675 proposes adding an API to set the "name" field that is currently EMPTY, but I'm not sure how we would use that in MongoDB to suppress this warning.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: