[SERVER-17039] db.currentOp() needs to display locking information Created: 25/Jan/15 Updated: 19/Sep/15 Resolved: 11/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Diagnostics |
| Affects Version/s: | 2.8.0-rc5 |
| Fix Version/s: | 3.0.0-rc9, 3.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Participants: |
| Description |
|
As part of The idea is to restore this information which is important for MMAPv1 diagnostics and included timeAcquiringMicros and timeLockedMicros. However, the whole lock mgr state is dumped into each operation, which vastly expands the size of the returned document with unhelpful information.
|
| Comments |
| Comment by Githook User [ 11/Feb/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This reintroduces the per-operation locking statistics. Also reverts commit 9b1392162e0f7564cfc3b1634ab78ec1a7f7c871. (cherry picked from commit 6e2d6ae03be6592d95334c43a726cde10247bd24) |
| Comment by Githook User [ 11/Feb/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This reintroduces the per-operation locking statistics. Also reverts commit 9b1392162e0f7564cfc3b1634ab78ec1a7f7c871. |
| Comment by Githook User [ 27/Jan/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: The way this information is presented in there currently is wrong and (cherry picked from commit 9b1392162e0f7564cfc3b1634ab78ec1a7f7c871) |
| Comment by Githook User [ 27/Jan/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: The way this information is presented in there currently is wrong and |