[SERVER-1931] curop should show op num of parent ops Created: 12/Oct/10  Updated: 06/Dec/22  Resolved: 09/Mar/18

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

Type: New Feature Priority: Major - P3
Reporter: Aaron Staple Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-387 currentOp() and killOp() don't work r... Closed
is related to SERVER-1928 evald fails in small oplog test Closed
Assigned Teams:
Query
Participants:
Case:

 Description   

If a db.eval parent op is constantly generating new child ops, the parent op is unlikely to be visible with currentOp. The currentOp implementation should show an op's parent's num so a user can kill the parent.

Alternatively currentOp could show the full op info for parent ops.



 Comments   
Comment by Ian Whalen (Inactive) [ 14/Jul/17 ]

Sending to Query but suspect this might just get resolved as won't fix since this is only helpful with dbdirectclient.

Comment by Asya Kamsky [ 08/Mar/15 ]

do we need this for any reason other than db.eval?

Comment by Aaron Staple [ 14/Dec/10 ]

Just to be clear, in the killop implementation when we kill the child the parent doesn't get killed. But if we kill the parent the child does get killed.

Generated at Thu Feb 08 02:58:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.