Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Storage Engines, Storage Engines - Foundations, Storage Engines - Persistence
Sprint:
None
Story Points:
5

Estimated Weeks:
0

This ticket encapsulates the work that needs to be done to understand why the connection->close() API call may return EBUSY.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

wt-conn-close-ebusys.png
1021 kB
Jun 02 2025 02:08:51 AM UTC
wt-conn-close-ebusys.svg
74 kB
Jun 02 2025 02:09:14 AM UTC

is related to

WT-14317 Create macro which aborts when conn->close() returns an error code

Closed

WT-15029 Abort when closing a file during shutdown returns an error code

Needs Scheduling

WT-14648 Fix log subsystem returning EBUSY from conn->close()

Closed

related to

SERVER-95136 Shutdown incorrectly assumes that WT_CONNECTION::close always succeeds

Closed

Assignee:: Unassigned
Reporter:: Etienne Petrel
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Jun 02 2025 01:48:13 AM UTC
Updated:: Jul 17 2025 06:09:42 AM UTC