[SERVER-5605] db.currentOp() - "query" : {"$msg" : "query not recording (too large)" Created: 14/Apr/12  Updated: 29/Nov/16  Resolved: 25/May/12

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

Type: Question Priority: Minor - P4
Reporter: joe piscitella Assignee: Daniel Crosta
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ubuntu 11.04


Issue Links:
Depends
Related
is related to SERVER-13952 Cache partial BSONObj if possible (in... Closed
Participants:

 Description   

how do you know what is running when you look at its simply states: "query" : {"$msg" : "query not recording (too large)"

db.currentOp()
"opid" : -2016542264,
"active" : false,
"lockType" : "write",
"waitingForLock" : true,
"op" : "update",
"ns" : "",
"query" :

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

,
"client" : "X.X.X.X:42135",
"desc" : "conn",
"threadId" : "0x7f10f7cf8700",
"connectionId" : 754951,
"numYields" : 0



 Comments   
Comment by Brad Vogel [ 29/Nov/16 ]

Filed https://jira.mongodb.org/browse/SERVER-27212. Thanks!

Comment by Ramon Fernandez Marina [ 15/Oct/16 ]

brad@mixmax.com, I couldn't find a specific ticket to allow users to decide how large is too large a message to log. For future reference, when in doubt, feel free to always open a ticket – it can always be deduplicated later.

Regards,
Ramón.

Comment by Brad Vogel [ 20/Sep/16 ]

Is there an open bug on making this a setting?

Comment by Steve John [ 16/Apr/13 ]

It would greatly help troubleshooting if it could at least show the query.

Comment by faraz ahmed khan [ 15/Apr/13 ]

If the query is tool large and that is the reason why its not being shown then perhaps just omit the data and show the query?

Comment by Chris Lowe [ 15/Apr/13 ]

Surely if the server is able to execute a query then I should be able to see it from db.currentOp()? Not being able to view which queries are in flight is a very big problem when trying to diagnose issues on our server.

Comment by Robert Sindall [ 15/Apr/13 ]

We've run into this useless error message as well.

A more informative message would be preferred/helpful.

Comment by Daniel Crosta [ 25/May/12 ]

Unfortunately, there's no way to see what this query is, unless it also happens to show up in the server log.

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