[SERVER-18625] Discrepancy between lockTime and totalLock in serverStatus Created: 21/May/15 Updated: 06/Dec/22 Resolved: 15/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
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. |