[SERVER-35384] db.currentOp() doesn't show which user ran the query Created: 04/Jun/18 Updated: 06/Dec/22 Resolved: 08/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brad Vogel | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
Notice that the output doesn't include which account ran the query. |
||||||||
| Participants: | |||||||||
| Description |
|
In MongoDB 3.4, the command db.currentOp() doesn't show which mongo user is running the query. This information is critical to being able to call db.killOp() from the original account to kill a query - provided we don't have access to a superadmin account that can kill any query, such is the case of Mongo Atlas customers. |
| Comments |
| Comment by Asya Kamsky [ 08/Jun/18 ] |
|
Closing as this is duplicate of |