Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-13383

Review eviction logging debug levels

    • Storage Engines
    • 5
    • StorEng - 2024-09-03, 2024-09-03 Q3 Streams v1

       Some log levels create too much noise for the given level they are associated with. We need to review the usage of debug levels for eviction along with the logs themselves. For example eviction debug verbose 1 prints every page that gets evicted. Which adds lots of noise for what should be a level that adds debugging logs with minimal noise.

      0xadbc10:[1723443437:210570][595496:0x7f0c0a190300], t, file:T00001.wt, WT_CURSOR.insert: [WT_VERB_EVICT][DEBUG_1]: page 0x1cd98d0 (row-store leaf)
      

      This ticket covers the investigation process with the intention of creating specific actionable tickets during this process. Separate tickets should be created to adjust log verbosity levels and messages.

      One other goal of this ticket is to identify basic logs of each module and enable them by default with NOTICE/INFO to get them to be logged in the MongoDB log file. These should be a very minimal subset of logs and can be tracked in this ticket.

      Questions to consider during this investigation:

      • Is it good already?
      • What’s missing
      • Is some trace too noisy for DEBUG_1 if we want to run in production
      • Can we make better use of the levels 1 through 4

            Assignee:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Reporter:
            sean.watt@mongodb.com Sean Watt
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: