-
Type: New Feature
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
A maxTimeMS=0 is equivalent to not setting a maxTimeMS (i.e. it will never time out)
- depends on
-
CSHARP-790 Server automatically abort 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
-
RUBY-661 Add support for server automatically aborting queries/commands after user-specified time limit
- Closed
-
SERVER-2212 Server automatically abort queries/commands after user-specified time limit
- Closed
-
CDRIVER-228 Server automatically abort queries/commands after user-specified time limit
- Closed
-
NODE-58 Server automatically abort queries/commands after user-specified time limit
- Closed
-
RUBY-699 server_op_timeout -> max_time_ms per spec
- Closed