[SERVER-17699] "locks" section empty in diagnostic log and profiler output for some operations Created: 23/Mar/15 Updated: 19/Sep/15 Resolved: 24/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Storage |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.0.2, 3.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Sprint: | Quint Iteration 3.1.1 |
| Participants: |
| Description |
|
The "locks" section in the diagnostic log and profiler output is empty for some operations, including basic reads. Example diagnostic log output exhibiting the problem (note "locks:{}" towards the end of the log line):
|
| Comments |
| Comment by Githook User [ 26/Mar/15 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: (cherry picked from commit d5f0d74d5c4a75a74e1d506ba224e54ee57f9a0b) |
| Comment by Githook User [ 24/Mar/15 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: |