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

Enable verbose messages few seconds before calling cache stuck

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 5
    • Storage - Ra 2022-01-10, Storage - Ra 2022-01-24, Storage - Ra 2022-02-07

      I got his idea while helping with a hard to reproduce cache stuck issue.

      We can potentially enable verbose messages N seconds before we decide that the cache is stuck long enough. Other than a dump of cache state, this will help us have some verbose messages about what the system was doing, specifically the eviction server and the workers. Were we still walking the cache to find pages? Were the pages being attempted to evict but failing repeatedly, etc.

      On the other hand, if we try it out and see that the verbose messages we are getting are not useful, it would be a motivation to fix what messages we record.

      It should be relatively easy to code, with a few lines of change I believe. I would say 10 seconds worth of verbose messages should be enough. I would prefer all verbosity rather than just eviction related in this case.

        1. with_verbose_log.txt
          71.98 MB
        2. without_verbose_log.txt
          2 kB

            Assignee:
            bing.xu@mongodb.com Bing Xu (Inactive)
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: