Kill Idle Transactions¶
This feature limits the age of idle transactions, for all transactional storage engines. If a transaction is idle for more seconds than the threshold specified, it will be killed. This prevents users from blocking InnoDB purge by mistake.
In Percona Server for MySQL 5.6.35-80.0
this feature has been re-implemented by
setting a connection socket read timeout value instead of periodically scanning
the internal InnoDB transaction list.
Version Specific Information¶
5.6.11-60.3
:- Feature ported from Percona Server for MySQL 5.5
5.6.35-80.0
:- Feature re-implemented using socket timeouts
System Variables¶
-
variable
innodb_kill_idle_transaction
¶ Version Info: - 5.6.11-60.3 – Introduced
- 5.6.35-80.0 – Variable is now an alias of
kill_idle_transaction
Scope: GLOBAL
Config: YES
Dynamic: YES
Variable Type: INTEGER
Default Value: 0 (disabled)
Units: Seconds
To enable this feature, set this variable to the desired seconds wait until the transaction is killed. NOTE: This variable has been deprecated and it will be removed in a future major release.
-
variable
kill_idle_transaction
¶ Version Info: - 5.6.35-80.0 – Variable implemented
Scope: GLOBAL
Config: YES
Dynamic: YES
Variable Type: INTEGER
Default Value: 0 (disabled)
Units: Seconds
If non-zero, any idle transaction will be killed after being idle for this many seconds.
Contact Us
For free technical help, visit the Percona Community Forum.To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or professional services, contact Percona Sales.