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

Discrepancy between lockTime and totalLock in serverStatus

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.3
    • Component/s: Diagnostics
    • None
    • Storage Execution
    • ALL

      As reported by customers:

      "total lock time" -> "locks(micros) w: 1629310"

      "global lock wait time", -> a quantity that constitutes part of "locks(micros) w:" but is not explicitly broken out in 2.6 logging and therefore is unknowable. It can be bounded as at least 1629310us / 1000 - 815ms = 814ms and at most 1629ms. (And it's a coincidence that the ratio is almost exactly 2:1.)

      "total time" -> "815ms" at end of line, to which we'd have to add the (unknowable) "global lock wait time" to get an (unknowable) total, total time.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: