From the design,
"Motivation:
The "oldest" open transaction in WiredTiger will pin write history in cache until it finishes. Here, "oldest" means the read timestamp is the earliest of any open transaction on the system. Any write history with a timestamp equal to or newer than this read timestamp must stay pinned in cache, in order to serve the open transaction. We need a way to prevent these transactions from staying open too long, in order to prevent cache pressure from becoming too extreme."
Adding a transactionLifetimeLimitSeconds server parameter, which can be set at startup and via setParameter. Transaction will now expire, per the server parameter, and be asynchronously periodically cleaned up.
- depends on
-
SERVER-34076 Add TransactionLifetimeLimit as a server parameter
-
- Closed
-
- is depended on by
-
SERVER-34486 Set transactionLifetimeLimitSeconds=1 in the fuzzer suites that run with replication enabled
-
- Closed
-
- is documented by
-
-
- Closed
-
- is related to
-
SERVER-35114 Make it possible to adjust the period of active jobs in the PeriodicRunner
-
- Closed
-