Details
-
Improvement
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
ServerDocs: May18-May22
-
true
-
(copied to CRM)
Description
With multi-statement transaction support, MongoDB will more often hold locks for an extended period of time. As it can be hard for a user to figure out what causes the blocking, it may be useful for them to obtain the list of locks held, and which operations hold these locks.
The lockInfo command gives this information, but currently is a well-kept secret.
Documenting the command might help change that.
Attachments
Issue Links
- depends on
-
SERVER-46634 LockInfo results missing a layer of hierarchy
-
- Closed
-
- documents
-
SERVER-46360 Hang analyzer json logging improvement
-
- Closed
-
- duplicates
-
DOCS-8989 Add command to dump lock manager state
-
- Closed
-
- is related to
-
SERVER-39858 Provide a command to list all locks
-
- Closed
-
- related to
-
DOCS-7765 Flesh out documentation for 'externalish' commands
-
- Closed
-