Slow Query logs durationMillis differs from latency recorded in opLatencies serverStatus section

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The "durationMillis" in a slow query log looks at CurOp::elapsedTimeTotal, which doesn't factor in pauses. The latencies reported in the opLatencies serverStatusSection derives from elapsedTimeExcludingPauses. These two should be consistent.

      Separately, I think it could be beneficial to remove the concept of "pausing" from the CurOp timer and fold it into the queues logic as suggested in SERVER-131015.

            Assignee:
            Unassigned
            Reporter:
            Patrick Freed
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: