-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2025-08-04, CAR Team 2025-08-18
-
None
-
3
-
TBD
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
In order to ensure that dropping the sessions collection does not cause any issues for transactions and/or retryable writes, we would like to augment our existing transaction testing to have sessions collection drops in the background.
As part of this ticket we should both
- Introduce targeted tests to ensure that retryable writes and prepared transactions work correctly when the sessions collection is dropped
- Introduce a passthrough suite background hook which drops the sessions collection and (sometimes) forces a refresh of the sessions after the drop
The new hook should be plugged into our existing transaction passthrough suites preferably also with stepdowns. Additionally, we should lower the session timeout in this suite to ensure that the sessions collection drop behavior is the same when the timeout is shorter.
- depends on
-
SERVER-108423 Check Metadata Consistency can segfault if the collection disappears during UUID check
-
- Backlog
-
- related to
-
SERVER-106189 Remediate inconsistent sessions collection on sharded clusters
-
- Backlog
-