[SERVER-11185] Time-interrupted operations should not generate a log message by default Created: 15/Oct/13  Updated: 10/Dec/14  Resolved: 16/Oct/13

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

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-2212 Server automatically abort queries/co... Closed
Participants:

 Description   

> db.foo.find({a:1}).maxTimeMS(1)
error: { "$err" : "operation exceeded time limit", "code" : 50 }

2013-10-15T10:51:08.108-0400 [conn1] assertion 50 operation exceeded time limit ns:test.foo query:{ query: { a: 1.0 }, $maxTimeMS: 1.0

The log message should be suppressed by default.



 Comments   
Comment by Siyuan Zhou [ 16/Oct/13 ]

Working on QA-356, I found only some queries and commands logging error messages, but the formats of error messages are arbitrary. Others, like findAndModify, text and aggregation, don't log anything when killed by maxTimeMS timeout.

 
// for query with javascript
2013-10-09T16:14:17.167-0400 [conn4] assertion 13475 JavaScript execution terminated ns:test.foo query:{ query: { $where: "sleep(2)" }, $maxTimeMS: 10.0 }
 
// for getmore
2013-10-09T16:14:43.252-0400 [conn4] getmore test.foo query: { query: {}, $maxTimeMS: 1.0 } cursorid:56915811531080108 ntoreturn:0 keyUpdates:0 exception: operation exceeded time limit code:50 locks(micros) r:1966 nreturned:1 reslen:75 1ms
 
// for count command
2013-10-09T16:19:17.535-0400 [conn4] Count with ns: test.foo and query: { j: 1.0 } failed with exception: 50 operation exceeded time limit code: 50
 
// for eval
2013-10-16T10:57:21.634-0400 [conn2] JavaScript execution terminated
 
// for group
2013-10-16T10:57:22.927-0400 [conn2] JavaScript execution terminated
 
// for mapreduce
2013-10-16T10:57:22.977-0400 [conn2] Assertion: 50:count failed in DBDirectClient: 50 operation exceeded time limit
2013-10-16T10:57:23.010-0400 [conn2] 0x103bde293
 0   mongod                              0x0000000103bde293 _ZN5mongo15printStackTraceERSo + 35

Comment by Eliot Horowitz (Inactive) [ 16/Oct/13 ]

I disagree

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