-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Foundations
-
None
-
None
Currently, it appears that we can have concurrent Connection API calls that use the default session. Sessions are not thread safe, so at first glance this seems like it should be a problem. However, we have not seen obvious failures, which suggests there may be some existing protection, or an incorrect assumption in our understanding.
Given that this could be a long standing behavior, this ticket is intentionally scoped as investigatory only.
- is related to
-
WT-16510 test/format (multi-node, disagg) Race condition in __wti_conn_dhandle_outdated leads to use-after-free dereference of session->dhandle
-
- Closed
-