彪悍的人生,niubility 参数 innodb_kill_idle_transaction

简介:

roidba 一直推崇看官方文档,自己做实验测试,只要这样才能成为一名合格的DBA。

锻炼自己的动手能力。

Kill Idle Transactions (mariadb &percona server 支持)

解决开发写SQL不commit 问题

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 5.7.17-11 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.7.10-1:

Feature ported from Percona Server 5.6

5.7.17-11:

Feature re-implemented using socket timeouts

System Variables

variable innodb_kill_idle_transaction

Version Info:

5.7.17-11 – 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.7.17-11 – 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.


官网链接

https://www.percona.com/doc/percona-server/LATEST/management/innodb_kill_idle_trx.html










本文转自 roidba 51CTO博客,原文链接:http://blog.51cto.com/roidba/1896257,如需转载请自行联系原作者
目录
相关文章
|
5月前
|
关系型数据库 MySQL 数据库
MySQL报错:Lock wait timeout exceeded; try restarting transaction
MySQL报错:Lock wait timeout exceeded; try restarting transaction
|
10月前
|
SQL 关系型数据库 MySQL
MySQL因为hung住,自动重新启动,InnoDB: Semaphore wait has lasted > 600 seconds
从错误日志中检查,有两个信号量等待时间超长,MySQL自动crash了
247 0
|
5月前
|
SQL 关系型数据库 MySQL
MySQL报错:1205 Lock wait timeout exceeded; try restarting transaction处理
MySQL报错:1205 Lock wait timeout exceeded; try restarting transaction处理
|
6月前
|
SQL 关系型数据库 MySQL
【MySQL异常】MySQL事务锁问题----lock wait timeout exceeded; try restarting transaction
【MySQL异常】MySQL事务锁问题----lock wait timeout exceeded; try restarting transaction
50 0
|
9月前
|
SQL 关系型数据库 MySQL
Mysql 异常:Lock wait timeout exceeded; try restarting transaction的解决办法
Mysql 异常:Lock wait timeout exceeded; try restarting transaction的解决办法
103 0
|
9月前
|
SQL 关系型数据库 MySQL
mysql Lock wait timeout exceeded; try restarting transaction解决方案
在测试程序时,打的断点怎么都跳不进去,console一直报 “Lock wait timeout exceeded; try restarting transaction”
108 0
|
9月前
PG14中的idle_session_timeout
PG14中的idle_session_timeout
54 0
|
10月前
|
SQL 关系型数据库 MySQL
|
关系型数据库 MySQL
jdbs学习中的错误总结1(MySql Lock wait timeout exceeded)
错误原因: 两个事物之间出现死锁,导致另外一个事物超时 某一种表频繁被锁表,导致其他事物无法拿到锁,导致事物超时
jdbs学习中的错误总结1(MySql Lock wait timeout exceeded)
|
关系型数据库
InnoDB redo log thread cpu usage
InnoDB 在8.0 里面把写redo log 角色的各个线程都独立出来, 每一个thread 都处于wait 状态, 同样用户thread 调用log_write_up_to 以后, 也会进入wait 状态.这里的wait 等待最后都是通过调用 os_event_wait_for 来实现, 而 os_event_wait_for 是先spin + wait 的方式实现.所以这里有两个参数会影响os_event_wait_for 函数:spins_limit,timeout.
115 0

热门文章

最新文章