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

Profiler entries may omit execStats metrics

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Querying
    • Query Execution
    • ALL

    Description

      Towards the end of find command execution, we call endQueryOp to fill out some CurOp metrics. Among these is OpDebug::execStats, which we populate only after checking that the operation is eligible for profiling.

      However, the CurOp timer continues to tick after this point. If the operation's duration is below the slowMS threshold when we check profiling eligibility in endQueryOp but has exceeded slowMS by the time we check again at the very end of the command code path, then we will incorrectly profile the operation without execStats.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            bernard.gorman@mongodb.com Bernard Gorman
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: