Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Diagnostics
Labels:
None

Assigned Teams:

Query
Case:
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

is related to

SERVER-1928 evald fails in small oplog test

Closed

related to

SERVER-387 currentOp() and killOp() don't work right with db.eval()

Closed

Assignee:: Backlog - Query Team (Inactive)
Reporter:: Aaron Staple (Inactive)
Participants:: Aaron Staple, Asya Kamsky, Backlog - Query Team, Ian Whalen
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Oct 12 2010 05:18:17 PM UTC
Updated:: Dec 06 2022 05:47:42 AM UTC
Resolved:: Mar 09 2018 09:48:12 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates