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

OOM kill detection in testing

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Evergreen
    • Storage Engines
    • 5
    • StorEng - Defined Pipeline

      While triaging WT-12894, Mick observed that the "real" bug was test/format getting OOM-killed. We may not pick up OOM via the exit code, so we should add some way to detect this.

      Some ideas include (but are not limited to!):

      • A grep in /var/log/messages or /var/log/kern.log for kill to confirm the OOM in these cases
      • Asking systemd what got OOM-killed

      This should be plumbed in such a way that it's easy to add a BBUI rule to detect these. It should also not be limited to test/format, ideally being extended to all WT testing.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            will.korteland@mongodb.com Will Korteland
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: