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

Add observability on the last thread that accessed a session

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • StorEng - Refinement Pipeline

      This will help diagnose a class of issues described in SERVER-61116. Today, we have a wealth of diagnostics on the WT sessions and on the thread state, however it's not straightforward to map a session to the thread that last accessed it.
       
      It would be useful to report this session -> thread mapping in a way that's readily accessible both on a live mongod process and in a core dump, such as those generated when a MongoDB integration test times out.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            josef.ahmad@mongodb.com Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: