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

Improve shutdown logging

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT11.3.0, 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: Checkpoints
    • None
    • Storage Engines
    • 3
    • StorEng - 2024-10-15

      HELP-57227 involved a shutdown that took ~4minutes. We should improve the WiredTiger logs to make it clear what is occurring during shutdown. The logs from the HELP ticket show:

      {"t":{"$date":"2024-02-22T05:09:06.579+00:00"},"s":"I",  "c":"STORAGE",  "id":4795902, "ctx":"thread695221","msg":"Closing WiredTiger","attr":{"closeConfig":"leak_memory=true,"}}
      {"t":{"$date":"2024-02-22T05:12:07.931+00:00"},"s":"I",  "c":"STORAGE",  "id":4795901, "ctx":"thread695221","msg":"WiredTiger closed","attr":{"durationMillis":181352}}
      

      With no WiredTiger logs in between.

      One question that was raised was:
      Is checkpoint initiated by WT as part of shutdown?

      We should ensure the logs make this clear and possibly add logs to indicate if checkpoint is taking a long time due to the amount of dirty content.

            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: