-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
QE 2025-06-23, QE 2025-07-07, QE 2025-07-21, QE 2025-08-04, QE 2025-08-18, QE 2025-09-01, QE 2025-09-15, QE 2025-10-13, QE 2025-10-27, QE 2025-12-08, QE 2025-11-24, QE 2025-11-10
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Leaked cursors can be due to a server bug. Currently, they go unnoticed.
Note that some workloads intentionally leave open cursors during their execution. For those, we should make sure they get closed by the `teardown` phase.
- is related to
-
SERVER-74994 Kill FSM worker thread sessions at the end of their execution
-
- Closed
-
- related to
-
SERVER-114502 Investigate agg_lookup and long_secondary_reads fsm tests leaking cursors
-
- Backlog
-
-
SERVER-114500 Investigate snapshot_read* FSM tests leaking cursors
-
- Backlog
-
-
SERVER-114503 Investigate DDL commands FSM tests leaking cursors
-
- Backlog
-