-
Type: New Feature
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Admin, Diagnostics, Querying
-
Query
-
Fully Compatible
-
Query 2018-07-16, Query 2018-07-30
-
(copied to CRM)
Allow access to the list of active cursors.
This should allow returning something like this:
> db.runCommand("listCursors") { ok:1.0, cursors: [ { id:..., ns:..., query:..., client:..., created:...., lastAccess:..., noTimeout:.., timeoutInMS:..., runningMS:..., yieldNum:..., user:..., nReturned:..., nPosition:..., ...} //recordStats/locks/curOp-info/etc ] }
This command should be user-aware and only return cursors for the active user.
Paramters:
name | value | desc/behavior |
---|---|---|
filter | <any query filter>, {id:###} | This should allow a filter/match param to reduce the total set of cursors returned. |
ns/db | filters to this ns/db – command name value is the default for this if not true-ish | |
user | <current> | This command should be user-aware and only return cursors for the active user. Optionally this should allow overriding to return all user info if the user has privs |
- is depended on by
-
SERVER-14047 endless "moveChunk failed, because there are still n deletes from previous migration"
- Closed
- is duplicated by
-
SERVER-5816 Add command to get a list of open cursors
- Closed
-
SERVER-1919 cursor info option to get detailed info about a specifc cursor or all
- Closed
- related to
-
SERVER-5813 Create a shell helper to kill a cursor by id
- Closed
-
SERVER-19982 Log diagnostic message when creating "no timeout" cursors
- Backlog