[SERVER-20323] db.currentOp(True) does not return operation ids for inactive operations Created: 09/Sep/15 Updated: 11/Dec/15 Resolved: 11/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 3.0.7, 3.2.0-rc2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ambikesh Kumar Shukla | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
I run db.currentOp(true) on mongoshel(2.6.9), this method returns information on all operations, including operations on idle connections and system operations(contain multiple operation ids.connection ids and multiple client ). When I ran same command On MongoShell(3.0.6) this return only multiple connection ids ,few operation ids and single client. This bug is fixed on issue no : When I ran same command On MongoShell(3.1.7) this return only multiple connection ids ,single operation id and multiple client. Please refer attachment for changing in results : first.jpeg |
| Comments |
| Comment by J Rassi [ 11/Dec/15 ] |
|
I'm closing this ticket as "Works as Designed". The v2.6 behavior was incorrect in displaying information about operations that have already completed. In 3.0.0 and later, this misleading information was intentionally removed. |