-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: CRUD
-
None
-
(copied to CRM)
-
None
-
None
-
None
-
None
-
None
-
None
-
None
To enable the use of context deadlines and timeouts we need to ensure that we don't send a request if a deadline is approaching. For tailable await cursors, we can set maxTimeMS, which will help ensure the server returns within a desirable amount of time.
If a context is cancelled or we do exceed the deadline, the cursor needs to be closed (and potentially killed), and the socket that was used needs to be closed.
- is duplicated by
-
GODRIVER-1036 Skipped change events when using a context timeout on stream.Next in a change stream
-
- Closed
-
- related to
-
-
- Closed
-