[SERVER-1794] make CurOp query's lifespan same as the op - so we can just keep a pointer Created: 14/Sep/10  Updated: 06/Dec/22  Resolved: 17/Feb/17

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

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 23
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-27439 Large queries can omit comment in cur... Closed
is duplicated by SERVER-13936 $comment vanishes when query is too big Closed
Related
is related to SERVER-16324 Command execution log line displays "... Closed
is related to SERVER-13935 Allow specifying profile entry and cu... Closed
is related to SERVER-13952 Cache partial BSONObj if possible (in... Closed
is related to SERVER-7677 Limit CurOp output to fixed size Closed
Assigned Teams:
Query
Participants:

 Description   

PRO: much faster
can see whole query
CON: can't see past ops - can always copy on exit for slow ops

Clean up duplicated data between CurOp and OpDebug or eliminate one



 Comments   
Comment by Tess Avitabile (Inactive) [ 17/Feb/17 ]

We believe this work is being tracked by SERVER-27439, which ensures that the comment is available. SERVER-27439 is in progress, and we have future plans to entirely remove truncation behavior in CurOp.

Comment by Chad Kreimendahl [ 30/Jun/14 ]

Is there a method to increase this from 256 bytes to something larger? We're trying to monitor slow queries and most of them that hit (> 50ms) are "too large"

Comment by Alan Cima [ 22/Jun/14 ]

How about just showing the comment field if there is one? That should be straightforward.

Comment by David Barshow [ 20/Jun/14 ]

Whats the status of this? Even a truncated string would be acceptable 99% of the time I would suspect

Comment by Eliot Horowitz (Inactive) [ 03/Jun/14 ]

Austin - the query will execute normally, just the reporting won't be in place.

Comment by Austin Riendeau [ 02/Jun/14 ]

When this occurs

{ $msg: "query not recording (too large)" }

, does mongo just drop the record or does it finish it?

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