Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-53180

Log each operation that holds a lock for an extended period of time without yielding

    XMLWordPrintable

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Diagnostics, Logging
    • None
    • Execution Team 2021-11-01, Execution Team 2021-11-15, Execution Team 2021-11-29, Execution Team 2021-12-13, Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-01-24, Execution Team 2022-02-07, Execution Team 2022-02-21

    Description

      Anything that holds a lock for an extended period of time without yielding is a potential performance problem. An extended period of time might be 1 second but should be configurable for debugging purposes or if this creates too much noise in the logs.

      The unlock code should know how long the lock has been held and also know which connection this happens on so it will give us more information tying it back to the offending operation.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              dmitry.agranat@mongodb.com Dmitry Agranat
              Votes:
              7 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

                Created:
                Updated: