Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.5.4
Affects Version/s: None
Component/s: Querying
Labels:
- query_triage

Add { $maxTimeMS: <integer> } as a query option, and add { maxTimeMS: <integer> } as a command option to all commands. Operations that exceed their time limit will be aborted, and an error will be returned to the client. A cursor.maxTimeMS() shell helper will be provided for queries.

Details:

An operation's "elapsed time" for the purpose of this feature will be the same as the operation's "elapsed time" as reported by the logging / profiling subsystems.
The abort semantics provided will be very similar to that of db.killOp():
- Operations cannot currently be interrupted while waiting to acquire a lock (but this will be supported when ~~SERVER-8579~~ is resolved).
- Write operations are generally not interruptible once the first write occurs.
- As a corollary, it is expected that operations which do not reach an interrupt point after exceeding the time limit will have an elapsed time longer than the time limit, and will be logged/profiled as such.
A query that completes in under its time limit will "roll over" its remaining time to the first getmore op (which will then "roll over" its remaining time to the second getmore op and so on, until the time limit is hit).
- Cursors returned by successful time-limited queries will still obey the default cursor idle timeout (unless the "no cursor idle timeout" flag has been set).
For now, insert/update/delete will not support time-limited operations.

depends on

SERVER-10550 CurOp::_killPending not always cleared between client operations

Closed

is depended on by

CSHARP-790 Server automatically abort queries/commands after user-specified time limit

Closed

DRIVERS-99 Add support for server automatically aborting queries/commands after user-specified time limit

Closed

JAVA-910 Support new $maxTimeMS field for all commands and queries

Closed

PYTHON-550 Support $maxTimeMS for commands and queries (MongoDB 2.6)

Closed

DOCS-1919 Document : Server automatically abort queries/commands after user-specified time limit

Closed

is duplicated by

SERVER-6761 db.coll.find(...).timeout(3000) should force the query to abort after 3000 ms

Closed

SERVER-3379 Query Timeout

Closed

is related to

SERVER-10382 Interrupted count commands don't return an error code

Closed

SERVER-10995 Elapsed time for $maxTimeMS queries includes time to acquire db lock

Closed

SERVER-11216 Interrupted geoNear commands on mongos don't return an error code

Closed

SERVER-11221 maxTimeMS(0.1) should return error

Closed

SERVER-11488 Supported mongos commands should propagate maxTimeMS option to shards

Closed

SERVER-11243 Add server status counter "time limit exceptions"

Closed

SERVER-6113 Uneven distribution of yields are unfair

Backlog

SERVER-8499 Server Side setting for Max query execution time

Backlog

SERVER-11094 Javascript interruption should use semantic "operation interrupted" error codes

Closed

SERVER-11185 Time-interrupted operations should not generate a log message by default

Closed

SERVER-11361 RunOnAllShardsCommand::run() should set "code" on error, if appropriate

Closed

SERVER-4477 Interrupting compact can cause drop of collection indexes

Closed

related to

SERVER-3960 High CPU usage no IO Wait

Closed

DOCS-9823 Document maxTimeMS option for all CRUD commands

Closed

(1 is depended on by, 2 is duplicated by, 12 is related to, 2 related to)

Assignee:: J Rassi

Reporter:: ppalka

Participants:: Adrien Mogenet, Alexey Palazhchenko, auto, Chelliah Thirunavukkarasu, J Rassi, ppalka, Victor

Votes:: 35 Vote for this issue

Watchers:: 40 Start watching this issue

Created:: Dec 13 2010 04:04:10 PM UTC

Updated:: Feb 28 2023 08:31:06 PM UTC

Resolved:: Nov 14 2013 01:29:17 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates