Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- greenerbuild

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Sprint:
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 2026-01-19, QE 2025-12-08, QE 2025-11-24, QE 2025-11-10, QE 2026-02-02, QE 2026-02-16
Linked BF Score:
200
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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.

causes

SERVER-119776 Disable checkIdleCursors hook for select Cluster Scalability tests

Closed

is related to

SERVER-74994 Kill FSM worker thread sessions at the end of their execution

Closed

related to

SERVER-114502 Investigate query fsm tests leaking cursors

Backlog

SERVER-119660 Ensure server_status_with_time_out_cursors.js does not leak cursors

Backlog

SERVER-114500 Investigate snapshot_read* FSM tests leaking cursors

Open

SERVER-114503 Investigate DDL commands FSM tests leaking cursors

Open

SERVER-121043 Reenable session clean-up in worker_thread.js

In Code Review

SERVER-119777 Re-enable checkIdleCursors hook for Cluster Scalability tests

Needs Scheduling

(3 related to)

Assignee:: Denis Grebennicov
Reporter:: Jordi Serra Torrens
Participants:: Denis Grebennicov, Githook User, Jordi Serra Torrens
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Mar 17 2023 03:31:37 PM UTC
Updated:: Mar 06 2026 01:32:30 AM UTC
Resolved:: Feb 13 2026 08:05:04 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates