When a cursor is opened as part of a session, its lifetime will be tied to that session. Closing or timing out of a session will kill all associated cursors. Given this, we can remove the separate cursor timeout mechanism for cursors that live as part of a session, and rely on session cleanup to handle cleanup of orphaned cursors.
- is depended on by
-
SERVER-57863 CursorNotFound since we doubled the number of shards
- Closed
-
PYTHON-938 aggregation cursor keepalive
- Closed
- is duplicated by
-
SERVER-6906 Potential cursor timeout at reduce stage of map reduce
- Closed
-
SERVER-13358 long aggregation queries get a cursor timeout error
- Closed
-
SERVER-57863 CursorNotFound since we doubled the number of shards
- Closed
-
SERVER-38123 Add a "cursor touch" call that would reset the cursor timeout without fetching the next document
- Closed
-
SERVER-46918 in a sharded db, cursor timeout on a shard while mongos is consuming the cursor on another shard
- Closed
-
SERVER-46885 Allow "refreshing" cursors as we can do with sessions
- Closed
-
SERVER-15895 Aggregation Query returning exception: Version 2.6
- Closed
- is related to
-
SERVER-27009 Replication initial sync creates cursors with no timeout
- Closed
-
SERVER-8188 Configurable idle cursor timeout
- Closed
- related to
-
SERVER-4800 mongos cursor handling with timeouts
- Closed
-
SERVER-26321 Long-running aggregations can artificially time out if the first batch takes more than 10 minutes
- Closed
-
SERVER-15042 Add noCursorTimeout option to command cursors
- Closed
-
SERVER-59573 Add setParameter which can be used to restore inactive cursor timeout in sessions
- Closed
-
DRIVERS-1602 Automate session refresh for long-lived cursors
- Backlog