[SERVER-8622] serverStatus blocks waiting for various locks Created: 19/Feb/13 Updated: 06/Dec/22 Resolved: 23/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.4.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | 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 |
|
Here is a quick analysis of the locks hanging off serverStatus:
The biggest issue is the recordStats since that requires a read lock for each db. |
| Comments |
| Comment by Eric Milkie [ 23/Feb/17 ] | |
|
There will always be locking necessary to glean the information needed by the various serverStatus sections. | |
| Comment by Scott Hernandez (Inactive) [ 14/Nov/14 ] | |
|
In recent versions new sections also require new locking like storageEngine (wiredtiger) and rangeDelete, for example. | |
| Comment by Scott Hernandez (Inactive) [ 20/Feb/13 ] | |
|
To work around this issue you can conditionally disable sections from being run/displayed like this:
|