[SERVER-20598] db.currentOp command suppresses "client" information for idle connections Created: 24/Sep/15 Updated: 24/Sep/15 Resolved: 24/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Networking, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Ankit Kakkar | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
As per the documentation of db.currentOp: Changed in version 3.0: For some inactive background threads, such as an inactive signalProcessingThread, MongoDB suppresses various empty fields. It seems that any idle connections (not running any operation) are suppressing client information. For example, In MongoDB 3.0, idle connections to mongo shell are showing up like this:
Can client (ip/hostname) be included in the output? |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 24/Sep/15 ] |
|
dup of |