mysql 行锁排查

<pre name="code" class="html">mysql 锁表:

隔离级别使用RR:
mysql> SELECT @@GLOBAL.tx_isolation, @@tx_isolation;
+-----------------------+-----------------+
| @@GLOBAL.tx_isolation | @@tx_isolation  |
+-----------------------+-----------------+
| REPEATABLE-READ       | REPEATABLE-READ 

SESSION A:

mysql> show full processlist;
+----+------+-----------+------+---------+------+-------+-----------------------+
| Id | User | Host      | db   | Command | Time | State | Info                  |
+----+------+-----------+------+---------+------+-------+-----------------------+
|  1 | root | localhost | NULL | Query   |    0 | init  | show full processlist |
+----+------+-----------+------+---------+------+-------+-----------------------+
1 row in set (0.02 sec)

mysql> insert into test values(1,'a');
Query OK, 1 row affected (0.00 sec)

mysql> select * from test;
+------+------+
| id   | name |
+------+------+
|    1 | a    |
+------+------+
1 row in set (0.00 sec)

mysql>  show full processlist;
+----+------+-----------+--------+---------+------+-------+-----------------------+
| Id | User | Host      | db     | Command | Time | State | Info                  |
+----+------+-----------+--------+---------+------+-------+-----------------------+
|  1 | root | localhost | DEVOPS | Query   |    0 | init  | show full processlist |
|  2 | root | localhost | DEVOPS | Sleep   |    8 |       | NULL                  |
+----+------+-----------+--------+---------+------+-------+-----------------------+
2 rows in set (0.00 sec)

mysql> update test set name='b' where id=1;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql>  show full processlist;
+----+------+-----------+--------+---------+------+-------+-----------------------+
| Id | User | Host      | db     | Command | Time | State | Info                  |
+----+------+-----------+--------+---------+------+-------+-----------------------+
|  1 | root | localhost | DEVOPS | Query   |    0 | init  | show full processlist |
|  2 | root | localhost | DEVOPS | Sleep   |   34 |       | NULL                  |
+----+------+-----------+--------+---------+------+-------+-----------------------+
2 rows in set (0.00 sec)

SESSION B:
此时HANG：
mysql>mysql> update test set name='c100' where id=1;

SESSION B的信息:
mysql>  show full processlist;
+----+------+-----------+--------+---------+------+----------+----------------------------------------+
| Id | User | Host      | db     | Command | Time | State    | Info                                   |
+----+------+-----------+--------+---------+------+----------+----------------------------------------+
|  1 | root | localhost | DEVOPS | Query   |    0 | init     | show full processlist                  |
|  2 | root | localhost | DEVOPS | Query   |    2 | updating | update test set name='c100' where id=1 |
+----+------+-----------+--------+---------+------+----------+----------------------------------------+
2 rows in set (0.00 sec)

此时SESION B也就是Id=2 被堵塞,一直在更新

模拟 Id=1获取锁:

mysql>  show full processlist;
+----+------+----------------------+------+---------+------+-------+-----------------------+
| Id | User | Host                 | db   | Command | Time | State | Info                  |
+----+------+----------------------+------+---------+------+-------+-----------------------+
|  7 | root | 115.236.160.82:53073 | NULL | Sleep   |  184 |       | NULL                  |
|  8 | root | 115.236.160.82:53074 | NULL | Sleep   |  184 |       | NULL                  |
|  9 | root | localhost            | NULL | Query   |    0 | init  | show full processlist |
+----+------+----------------------+------+---------+------+-------+-----------------------+
3 rows in set (0.00 sec)

mysql> select * from test;
+------+------+
| id   | name |
+------+------+
|    1 | b    |
|    2 | b    |
|    2 | b    |
+------+------+
3 rows in set (0.00 sec)

SELECT
    r.trx_state wating_trx_state,
    r.trx_id waiting_trx_id,
    r.trx_mysql_thread_Id waiting_thread,
    r.trx_query waiting_query,
    b.trx_state blocking_trx_state,
    b.trx_id blocking_trx_id,
    b.trx_mysql_thread_id blocking_thread,
    b.trx_query blocking_query
FROM
    information_schema.innodb_lock_waits w
        INNER JOIN
    information_schema.innodb_trx b ON b.trx_id = w.blocking_trx_id
        INNER JOIN
    information_schema.innodb_trx r ON r.trx_id = w.requesting_trx_id

# wating_trx_state, waiting_trx_id, waiting_thread, waiting_query,                             blocking_trx_state, blocking_trx_id, blocking_thread, blocking_query
'LOCK WAIT',               '2332',          '10', 'update test set name=\'aabbcc100\' where id=1', 'RUNNING',          '2331',        '9',            NULL

mysql> desc information_schema.innodb_lock_waits
    -> ;
+-------------------+-------------+------+-----+---------+-------+
| Field             | Type        | Null | Key | Default | Extra |
+-------------------+-------------+------+-----+---------+-------+
| requesting_trx_id | varchar(18) | NO   |     |         |       |
| requested_lock_id | varchar(81) | NO   |     |         |       |
| blocking_trx_id   | varchar(18) | NO   |     |         |       |
| blocking_lock_id  | varchar(81) | NO   |     |         |       |
+-------------------+-------------+------+-----+---------+-------+
4 rows in set (0.00 sec)

REQUESTING_TRX_ID	ID of the requesting transaction.   请求事务的ID

REQUESTED_LOCK_ID	ID of the lock for which a transaction is waiting. Details about the lock can be found by joining with INNODB_LOCKS on LOCK_ID.

事务在等待的lockid ,详细的信息可以关联 INNODB_LOCKS on LOCK_ID

BLOCKING_TRX_ID	ID of the blocking transaction.

blocking 事务的 ID 持有者

BLOCKING_LOCK_ID	ID of a lock held by a transaction blocking another transaction from proceeding. Details about the lock can be found by joining with INNODB_LOCKS on LOCK_ID.

一个事务持有的lock ID 阻塞其他事务处理

mysql> desc information_schema.innodb_trx
    -> ;
+----------------------------+---------------------+------+-----+---------------------+-------+
| Field                      | Type                | Null | Key | Default             | Extra |
+----------------------------+---------------------+------+-----+---------------------+-------+
| trx_id                     | varchar(18)         | NO   |     |                     |       |
| trx_state                  | varchar(13)         | NO   |     |                     |       |
| trx_started                | datetime            | NO   |     | 0000-00-00 00:00:00 |       |
| trx_requested_lock_id      | varchar(81)         | YES  |     | NULL                |       |
| trx_wait_started           | datetime            | YES  |     | NULL                |       |
| trx_weight                 | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_mysql_thread_id        | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_query                  | varchar(1024)       | YES  |     | NULL                |       |
| trx_operation_state        | varchar(64)         | YES  |     | NULL                |       |
| trx_tables_in_use          | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_tables_locked          | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_lock_structs           | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_lock_memory_bytes      | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_rows_locked            | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_rows_modified          | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_concurrency_tickets    | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_isolation_level        | varchar(16)         | NO   |     |                     |       |
| trx_unique_checks          | int(1)              | NO   |     | 0                   |       |
| trx_foreign_key_checks     | int(1)              | NO   |     | 0                   |       |
| trx_last_foreign_key_error | varchar(256)        | YES  |     | NULL                |       |
| trx_adaptive_hash_latched  | int(1)              | NO   |     | 0                   |       |
| trx_adaptive_hash_timeout  | bigint(21) unsigned | NO   |     | 0                   |       |
| trx_is_read_only           | int(1)              | NO   |     | 0                   |       |
| trx_autocommit_non_locking | int(1)              | NO   |     | 0                   |       |
+----------------------------+---------------------+------+-----+---------------------+-------+
24 rows in set (0.00 sec)

TRX_ID  唯一的事务ID号, InnoDB内部使用.( 在MySQL 5.6开始,

那些IDs不是被创建用于事务的,是只读的和非堵塞的

TRX_WEIGHT  一个事务的权重, 反映(但是不是必须的准确的计数) 被改变的行和被事务锁定的行。

为了解决死锁, InnoDB 选择最小权重的事务作为 victim来回滚。

事务 改变非事务表是被认为比其他权重高, 不管更改的数目和锁住的行数

TRX_STATE   事务执行状态, RUNNING,LOCK WAIT, 回滚或者提交

TRX_STARTED	Transaction start time.  事务开始时间

TRX_REQUESTED_LOCK_ID  LOCK 事务ID 是当前等待(如果 TRX_STATE 是lock,否则为空)

TRX_WAIT_STARTED  当交易开始等待lock(如果TRX_STATE 是LOCK WAIT,否则NULL)

TRX_MYSQL_THREAD_ID

MySQL thread ID,可以用于关联PROCESSLIST 的ID
mysql>  show full processlist;
+----+------+-----------+--------+---------+------+-------+-----------------------+
| Id | User | Host      | db     | Command | Time | State | Info                  |
+----+------+-----------+--------+---------+------+-------+-----------------------+
|  1 | root | localhost | DEVOPS | Sleep   |    6 |       | NULL                  |
|  2 | root | localhost | DEVOPS | Query   |    0 | init  | show full processlist |
+----+------+-----------+--------+---------+------+-------+-----------------------+

见章节 14.13.2.3.1 ,潜在的不一致的PROCESSLIST数据

TRX_QUERY	 通过事务执行的SQL

TRX_OPERATION_STATE  事务的当前操作,或者为NULL

TRX_TABLES_IN_USE    Innodb表当前被使用来处理当前事务的SQL的表的数量

TRX_TABLES_LOCKED    InnoDB表当前SQL语句有行锁的表的数量。

因为这些是row locks, 不是表锁,表仍旧可以被读取和被多个事务写,尽管有些行被锁定。

TRX_LOCK_STRUCT        事务保留的锁的数目

TRX_LOCK_MEMORY_BYTES   这个事务的lock 结构在内存里占用的大小

TRX_ROWS_LOCKED 这个事务的锁定的大概记录的行数,

该值可能包括标记为删除的记录 物理上是存在的 但是对于事务不可见

TRX_ROWS_MODIFIED  在该事务中修改和插入的数目

TRX_CONCURRENCY_TICKETS  这个值表明 当前事务可以做多少事情在被交换出去之前,

通过 innodb_concurrency_tickets 选择指定

TRX_ISOLATION_LEVEL   当前事务的隔离级别

TRX_UNIQUE_CHECKS

是否 unique checks 被启用或者关闭 对于当前的事务, 它们可以在一个批量数据加载时关闭

时间： 2024-08-11 09:46:14

mysql 行锁排查的相关文章

mysql行锁和表锁

mysql innodb支持行锁和表锁,但是MyIsam只支持表锁.现在我们说说mysql innodb的行锁和有如下表id为主键为了出现演示效果,我们将mysql的autocommit设置为0 打开两个mysql命令行窗口,都设置为autocommit为0 窗口1: 窗口2: 这时候我们发现窗口2一直在阻塞,当我们在窗口1中commit后,发现窗口2有输出了. 上面我们更新不是同一个记录,为什么事物1没提交时,事物2一直等待了.因为这个时候用的是表锁. 现在我们给name字段加上索引,效果

数据库进阶之路（五） - MySQL行锁深入研究

由于业务逻辑的需要,必须对数据表的一行或多行加入行锁,举个最简单的例子,图书借阅系统:假设id=1的这本书库存为1,但是有2个人同时来借这本书,此处的逻辑为: SELECT restnum FROM book WHERE id =1 ; --如果restnum大于0,执行update UPDATE book SET restnum=restnum-1 WHERE id=1; 问题来了,当2个人同时借的时候,有可能第一个人执行select语句的时候,第二个人插了进来,在第一个人没来得及更新book

MySQL行锁深入研究

原文:http://blog.csdn.net/minipeach/article/details/5325161/ 做项目时由于业务逻辑的需要,必须对数据表的一行或多行加入行锁,举个最简单的例子,图书借阅系统.假设 id=1 的这本书库存为 1 ,但是有 2 个人同时来借这本书,此处的逻辑为 [php] view plain copy Select restnum from book where id =1 ; -- 如果 restnum 大于 0 ,执行 update Updat

mysql 行锁的实现

mysql锁的方式根据隔离级别不同而不同,因为默认隔离级别为repeatable-read可重复读,我们普遍理解为mysql锁实现方式为行锁,行锁就是利用索引实现完成的,mysql的支持的隔离级别有四种,这网上很多介绍,平常用的最多的也就是read-committed和repeatable-read两个,今天就对这两个隔离级别下锁的实现做下对比首先我们就用默认级别repeatable-read的隔离级别来做测试: mysql> CREATE TABLE `t1` ( -> `id` in

MySQL 行锁表锁机制

MySQL 表锁和行锁机制行锁变表锁,是福还是坑?如果你不清楚MySQL加锁的原理,你会被它整的很惨!不知坑在何方?没事,我来给你们标记几个坑.遇到了可别乱踩.通过本章内容,带你学习MySQL的行锁,表锁,两种锁的优缺点,行锁变表锁的原因,以及开发中需要注意的事项.还在等啥?经验等你来拿! MySQL的存储引擎是从MyISAM到InnoDB,锁从表锁到行锁.后者的出现从某种程度上是弥补前者的不足.比如:MyISAM不支持事务,InnoDB支持事务.表锁虽然开销小,锁表快,但高并发下性能低.行锁

mysql行锁+可重复读+读提交

行锁 innodb支持行锁,myisam只支持表锁,同一时刻每张表只能有一条数据被更新在InnoDB事务中,行锁是在需要的时候才加上的,但并不是不需要了就立刻释放, 而是要等到事务结束时才释放.这个就是两阶段锁协议. 如果你的事务中需要锁多个行,要把最可能造成锁冲突.最可能影响并发度的锁的申请时机尽量往后放. 例子:假设你负责实现一个电影票在线交易业务,顾客A要在影院B购买电影票.我们简化一点,这个业务需要涉及到以下操作: 从顾客A账户余额中扣除电影票价: 给影院B的账户余额增加这张电影票价

mysql 行锁，表锁测试

环境:mysql5.5,引擎innodb,SQLYOG 行锁,表锁区别:其实就是看where后面的条件是否有有索引,有索引的时候就是行锁,没有索引的时候就是表索. 先创建表结构: CREATE TABLE `lock_test` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(200) DEFAULT NULL, `age` int(11) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGI

MySQL 行锁、表锁

1. 多个事务操作同一行数据时,后来的事务处于阻塞等待状态.这样可以避免了脏读等数据一致性的问题.后来的事务可以操作其他行数据,解决了表锁高并发性能低的问题 2.InnoDB的行锁是针对索引加的锁,不是针对记录加的锁.并且该索引不能失效,否则都会从行锁升级为表锁.没有索引的字段更新会变为表锁. 3.间歇锁是指update where id >6 大于6 这个间隙.危害(坑):若执行的条件是范围过大,则InnoDB会将整个范围内所有的索引键值全部锁定,很容易对性能造成影响 1 InnoDB

MySQL行锁、间隙锁、Next-Key锁

InnoDB是一个支持行锁的存储引擎,它有三种行锁的算法: Record Lock:行锁,单个行记录上的锁. Gap Lock:间隙锁,锁定一个范围,但不包括记录本身.GAP锁的目的,是为了防止幻读.防止间隙内有新数据插入.防止已存在的数据更新为间隙内的数据. Next-Key Lock:1+2,锁定一个范围,并且锁定记录本身.对于行的查询,都是采用该方法,主要目的是解决幻读的问题.InnoDB默认加锁方式是next-key 锁. 这三种锁都是排它锁(X锁). 要详细了解间隙锁可以参考这篇文章: