-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
v8.0, v7.0, v6.0, v5.0
-
Execution Team 2024-08-19, Execution Team 2024-09-02, Execution Team 2024-09-16
-
0
-
5
The "abortExpiredTransactions" thread iterates over a list of expired sessions and tries to abort each one serially However, if, for some reason, one of the expired sessions cannot be checked out right away, the "abortExpiredTransactions" thread is blocked until the session can be checked out.
This can potentially prevent expired sessions from being reaped.
- is depended on by
-
COMPASS-8272 Investigate changes in SERVER-77172: "abortExpiredTransactions" thread can get stuck if it fails to checkout a session
- Closed
-
TOOLS-3662 Investigate changes in SERVER-77172: "abortExpiredTransactions" thread can get stuck if it fails to checkout a session
- Closed
- is duplicated by
-
SERVER-91632 Create a metrics.abortExpiredTransactions.totalAborted counter
- Closed
- is related to
-
SERVER-96559 Increase AbortExpiredTransactionsSessionCheckoutTimeout in kill_op_on_txn_expiry.js
- Closed
- related to
-
SERVER-64982 Extended lack of availability caused by transactions
- Blocked
-
WT-10958 Session API to roll-back a transaction if it is blocking eviction
- Open
-
SERVER-61251 Ensure long running storage engine operations are interruptible
- Backlog
- tested by
-
SERVER-94327 Add unittest for killAllExpiredTransactions
- Closed