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

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 5.2 Required
    • Component/s: Diagnostics, Logging
    • Labels:
      None
    • Case:

      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

              Assignee:
              backlog-server-execution Backlog - Storage Execution Team
              Reporter:
              dmitry.agranat Dmitry Agranat
              Participants:
              Votes:
              6 Vote for this issue
              Watchers:
              18 Start watching this issue

                Dates

                Created:
                Updated: