Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Engines, Storage Engines - Server Integration
Operating System:
ALL
Sprint:
SESI - 2025-10-14
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Right now if we allocate and release a cursor from a "stale" session – one with a non-current epoch, WiredTigerSession::releaseCursor() will notice it and simply drop the cursor on the floor. This can result in an undetected leak as in SERVER-110832. We should probably catch this; if there is no circumstance aside from shutdown we should be using a "stale" session we should assert here. Or at least when we create a new cursor from a "stale" session.

is related to

SERVER-110832 OplogWriter should not hold on to session through rollbacks

Open

SERVER-85167 Size storer can be flushed concurrently with being destructed for rollback

Closed

SERVER-93389 WiredTigerSessionCache does not properly dispose of sessions released after rollback

Closed

SERVER-110391 Release WT session when yielding resources

Open

Assignee:: Unassigned
Reporter:: Matthew Russotto
Participants:: Matthew Russotto
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Sep 12 2025 07:51:05 PM UTC
Updated:: Sep 18 2025 12:08:32 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates