-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
v8.0, v7.0, v6.0
-
Cluster Scalability 2024-07-22
-
0
reap_sessions_with_active_yielders.js tests that if a logical session expires while a transaction router is yielded, that prevents reaping the in-memory transaction state for that router's session. It simulates expiration by manually deleting from config.transactions with the default write concern, which can trigger the scenario from SERVER-92718 if a logical session cache refresh later reads from a stale secondary and does not see the deletion. The test is failing frequently enough and isn't meant to test the logic in SERVER-92718, so we should avoid failures by making it wait for the manual delete to replicate to all nodes before continuing the test.
- related to
-
SERVER-92718 Internal sessions in an expired logical session may be reaped earlier than expected
-
- Backlog
-