[SERVER-17982] currentOp can return an inactive operation with a missing "active" field Created: 10/Apr/15  Updated: 06/Dec/22  Resolved: 05/Aug/19

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 3.0.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Adam Midvidy Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query
Operating System: ALL
Participants:

 Description   

Caught by milkie.

There is an edge case in currentOp where we can neglect to report "active": false if opCtx is non-null but getCurOp() is null, when $all is passed.



 Comments   
Comment by David Storch [ 05/Aug/19 ]

Closing as Won't Fix per Bernard's comment above. milkie if you can recall any specific context around this original bug report, please let us know.

Comment by Bernard Gorman [ 02/Aug/19 ]

david.storch: it's difficult to say with complete certainty, because the ticket doesn't provide a link to where this was happening, and getCurOp() no longer exists in the codebase. But I'm not aware of any places in the current implementation where this could happen.

Comment by David Storch [ 02/Aug/19 ]

bernard.gorman do you know if this issue still exists after your work on the currentOp command?

Generated at Thu Feb 08 03:46:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.