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

currentOp's waitingForLatch field is misleading

    XMLWordPrintableJSON

Details

    • Service Arch

    Description

      Currently, if any Client thread is blocked in a call to waitForConditionOrInterrupt, it will show up in the currentOp output as both "active:true" and with a "waitingForLatch" field identifying the Mutex associated with the condition variable being waited on. This output suggests the Mutex (Latch?) is locked and that the code is blocked waiting to acquire it, but this is a false suggestion.

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: