-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
Certain CSOT behavior is "feature-gated" in pre-2.0 versions of the driver when Timeout is declared:
- Retrying all operations as many times as the context allows
- Automatic calculation and appension of “maxTimeMS”
- Using the min RTT as a threshold for “short-circuiting” (described in the “Command Execution” section)
In 2.0, fully remove all deprecated options and methods, and make the above behaviors the default (not gated by the presence of Timeout).
Definition of done:
- Update connectTimeoutMS to cover all blocking operations during connection establishment, including MongoDB handshake and auth.
- Remove all deprecated timeout options.
- All behavior conditionally enabled by the presence of a timeoutMS configuration should be the new default behavior.
- causes
-
GODRIVER-3322 Uploading a GridFS Stream with client-level timeout cancels context
- Closed
- fixes
-
GODRIVER-3151 Apply operation-level timeouts to maxTimeMS
- Closed
- has to be done after
-
GODRIVER-2342 Deprecate SocketTimeout, wTimeout, MaxTime and MaxCommitTime
- Closed
-
GODRIVER-2762 Use minimum RTT for CSOT maxTimeMS calculation instead of 90th percentile
- Closed
- is depended on by
-
GODRIVER-3181 Port "Read responses in the background after an operation timeout" to master
- Closed
- is related to
-
DRIVERS-2829 Create CSOT Legacy Timeout Analogues and Compatibility Field
- Ready for Work
-
GODRIVER-3266 TestCSOTProse fails on Windows CI Builds
- Closed