------------

1分钟内产生binlog大小计算

select @a1:=VARIABLE_VALUE as a1
from information_schema.GLOBAL_STATUS
where VARIABLE_NAME='innodb_os_log_written'
union all
select sleep(60)
union all
select @a2:=VARIABLE_VALUE as a2
from information_schema.GLOBAL_STATUS
where VARIABLE_NAME='innodb_os_log_written';

select round((@a2-@a1)/1024/1024/@@innodb_log_files_in_group) as MB;

---------------------

SELECT      
        p2.`HOST` Blockedhost,  
p2.`USER` BlockedUser,  
r.trx_id BlockedTrxId,      
        r.trx_mysql_thread_id BlockedThreadId,      
        TIMESTAMPDIFF(      
            SECOND,      
            r.trx_wait_started,      
            CURRENT_TIMESTAMP      
        ) WaitTime,      
        r.trx_query BlockedQuery,      
        l.lock_table BlockedTable,    
        m.`lock_mode` BlockedLockMode,  
        m.`lock_type` BlockedLockType,  
        m.`lock_index` BlockedLockIndex,  
        m.`lock_space` BlockedLockSpace,  
        m.lock_page BlockedLockPage,  
        m.lock_rec BlockedLockRec,  
        m.lock_data BlockedLockData,   
        p.`HOST` blocking_host,   
        p.`USER` blocking_user,  
        b.trx_id BlockingTrxid,      
        b.trx_mysql_thread_id BlockingThreadId,  
        b.trx_query BlockingQuery,  
        l.`lock_mode` BlockingLockMode,  
        l.`lock_type` BlockingLockType,  
        l.`lock_index` BlockingLockIndex,  
        l.`lock_space` BlockingLockSpace,  
        l.lock_page BlockingLockPage,  
        l.lock_rec BlockingLockRec,  
        l.lock_data BlockingLockData,           
       IF (p.COMMAND = 'Sleep', CONCAT(p.TIME,' seconds'), 0) idel_in_trx               
    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      
    INNER JOIN information_schema.INNODB_LOCKS l ON w.blocking_lock_id = l.lock_id  AND l.`lock_trx_id`=b.`trx_id`  
      INNER JOIN information_schema.INNODB_LOCKS m ON m.`lock_id`=w.`requested_lock_id` AND m.`lock_trx_id`=r.`trx_id`  
    INNER JOIN information_schema. PROCESSLIST p ON p.ID = b.trx_mysql_thread_id     
 INNER JOIN information_schema. PROCESSLIST p2 ON p2.ID = r.trx_mysql_thread_id   
    ORDER BY      
        WaitTime DESC;

--------------

SELECT      
        p2.`HOST` 被阻塞方host,  
p2.`USER` 被阻塞方用户,  
r.trx_id 被阻塞方事务id,      
        r.trx_mysql_thread_id 被阻塞方线程号,      
        TIMESTAMPDIFF(      
            SECOND,      
            r.trx_wait_started,      
            CURRENT_TIMESTAMP      
        ) 等待时间,      
        r.trx_query 被阻塞的查询,      
        l.lock_table 阻塞方锁住的表,    
        m.`lock_mode` 被阻塞方的锁模式,  
        m.`lock_type`  "被阻塞方的锁类型(表锁还是行锁)",  
        m.`lock_index` 被阻塞方锁住的索引,  
        m.`lock_space` 被阻塞方锁对象的space_id,  
        m.lock_page 被阻塞方事务锁定页的数量,  
        m.lock_rec 被阻塞方事务锁定行的数量,  
        m.lock_data  被阻塞方事务锁定记录的主键值,    
        p.`HOST` 阻塞方主机,  
        p.`USER` 阻塞方用户,  
        b.trx_id 阻塞方事务id,      
        b.trx_mysql_thread_id 阻塞方线程号,   
        b.trx_query 阻塞方查询,   
        l.`lock_mode` 阻塞方的锁模式,  
        l.`lock_type` "阻塞方的锁类型(表锁还是行锁)",  
        l.`lock_index` 阻塞方锁住的索引,  
        l.`lock_space` 阻塞方锁对象的space_id,  
        l.lock_page 阻塞方事务锁定页的数量,  
        l.lock_rec 阻塞方事务锁定行的数量,  
        l.lock_data 阻塞方事务锁定记录的主键值,           
      IF (p.COMMAND = 'Sleep', CONCAT(p.TIME,' 秒'), 0) 阻塞方事务空闲的时间             
    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      
    INNER JOIN information_schema.INNODB_LOCKS l ON w.blocking_lock_id = l.lock_id  AND l.`lock_trx_id`=b.`trx_id`  
      INNER JOIN information_schema.INNODB_LOCKS m ON m.`lock_id`=w.`requested_lock_id` AND m.`lock_trx_id`=r.`trx_id`  
    INNER JOIN information_schema. PROCESSLIST p ON p.ID = b.trx_mysql_thread_id     
 INNER JOIN information_schema. PROCESSLIST p2 ON p2.ID = r.trx_mysql_thread_id   
    ORDER BY      
        等待时间 DESC;

-------------------------------------------------------------------

# 查找有碎片的表:
select table_schema db, table_name, data_free, engine    
from information_schema.tables
where table_schema not in ('information_schema', 'mysql')  and data_free > 0;

SELECT TABLE_NAME,(DATA_LENGTH+INDEX_LENGTH)/1024/1024 size_mb,data_free/1024/1024 free_mb,TABLE_ROWS
FROM information_schema.tables where table_schema not in ('information_schema', 'mysql')
 and data_free/1024/1024>=1 order by free_mb desc;
---------------------------------------------------------------------------
#找出没有主键的表
Select t.table_schema,t.table_name,t.engine,t.table_rows
From information_schema.tables as t
 Left join information_schema.table_constraints as tc
 On tc.table_schema=t.table_schema
 And tc.table_name=t.table_name
 And tc.constraint_type='PRIMARY KEY'
 Where t.table_type='BASE TABLE'
 And tc.constraint_type is null
 And t.table_schema  not in ('mysql','performance_schema','information_schema');

------------------------------

ySQL中一些查看事务和锁情况的常用语句

一些查看数据库中事务和锁情况的常用语句

查看事务等待状况:

select
r.trx_id waiting_trx_id,
r.trx_mysql_thread_id waiting_thread,
r.trx_query waiting_query,
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;

查看更具体的事务等待状况:

select
b.trx_state,
e.state,
e.time,
d.state as block_state,
d.time as block_time,
a.requesting_trx_id,
a.requested_lock_id,
b.trx_query,
b.trx_mysql_thread_id,
a.blocking_trx_id,
a.blocking_lock_id,
c.trx_query as block_trx_query,
c.trx_mysql_thread_id as block_trx_mysql_tread_id
from
information_schema.innodb_lock_waits a
left join information_schema.innodb_trx b on a.requesting_trx_id = b.trx_id
left join information_schema.innodb_trx c on a.blocking_trx_id = c.trx_id
left join information_schema.processlist d on c.trx_mysql_thread_id = d.id
left join information_schema.processlist e on b.trx_mysql_thread_id = e.id
order by
a.requesting_trx_id;

查看未关闭的事务:
–mysql 5.6

select
a.trx_id,
a.trx_state,
a.trx_started,
a.trx_query,
b.id,
b.user,
b.db,
b.command,
b.time,
b.state,
b.info,
c.processlist_user,
c.processlist_host,
c.processlist_db,
d.sql_text
from
information_schema.innodb_trx a
left join information_schema.processlist b on a.trx_mysql_thread_id = b.id
and b.command = 'sleep'
left join performance_schema.threads c on b.id = c.processlist_id
left join performance_schema.events_statements_current d on d.thread_id = c.thread_id;

–mysql 5.5

select
a.trx_id,
a.trx_state,
a.trx_started,
a.trx_query,
b.id,
b. user,
b. host,
b.db,
b.command,
b.time,
b.state,
b.info
from
information_schema.innodb_trx a
left join information_schema.processlist b on a.trx_mysql_thread_id = b.id
where
b.command = 'sleep';

查看某段时间以来未关闭事务:

select
trx_id,
trx_started,
trx_mysql_thread_id
from
information_schema.innodb_trx
where
trx_started < date_sub(now(), interval 1 minute)
and trx_operation_state is null
and trx_query is null;

 

MySql检测阻塞,锁等待sql的更多相关文章

  1. MySQL找出锁等待

    1.服务器级别的锁等待 可以通过show processlist看到等待锁的线程id,但是无法知道究竟哪个线程持有锁 可以通过mysqladmin debug 相关等待锁的线程以及谁持有锁可以在错误日 ...

  2. MySQL自增锁等待问题解决

    有网友再群里问:在做基准测试时候,批量插入数据时,有很多自增锁等待,我告诉他解决办法: 1.innodb_autoinc_lock_mode=2 2.innodb_autoextend_increme ...

  3. mysql 开发进阶篇系列 13 锁问题(关于表锁,死锁示例,锁等待设置)

    一. 什么时候使用表锁 对于INNODB表,在绝大部分情况下都应该使用行锁.在个别特殊事务中,可以考虑使用表锁(建议). 1. 事务需要更新大部份或全部数据,表又比较大,默认的行锁不仅使这个事务执行效 ...

  4. MySQL事务锁等待超时 Lock wait timeout exceeded; try restarting transaction

    工作中处理定时任务分发消息时出现的问题,在查找并解决问题的时候,将相关的问题博客收集整理,在此记录下,以便之后再遇到相同的问题,方便查阅. 问题场景 问题出现的场景: 在消息队列处理消息时,同一事务内 ...

  5. MySQL锁等待分析【1】

    场景: 昨天业务系统上遇到了数据库慢的问题(对dcsdba.og_file_audit表的insert 慢&超时).分析后定位到是由于锁等待造成的.分析过程如下: 1.执行show proce ...

  6. MySQL Innodb如何找出阻塞事务源头SQL

    在MySQL数据库中出现了阻塞问题,如何快速查找定位问题根源?在实验开始前,我们先梳理一下有什么工具或命令查看MySQL的阻塞,另外,我们也要一一对比其优劣,因为有些命令可能在实际环境下可能并不适用. ...

  7. MySQL Backup--Xtrabackup备份设置锁等待问题

    问题描述 innobackupex备份过程需要保证备份数据一致性,通过刷新表缓存和加全局读锁(FLUSH TABLES WITH READ LOCK)获取备份位点,而为防止锁等待超时,会先设置: SE ...

  8. MySQL锁等待分析【2】

    MySQL锁等待分析[1]中对锁等待的分析是一步一步来的.虽然最后是分析出来了,可是用时是比较长的:理清各个表之间的关系后,得到如下SQL语句,方便以后使用 select block_trx.trx_ ...

  9. mysql InnoDB锁等待的查看及分析

    说明:前面已经了解了InnoDB关于在出现锁等待的时候,会根据参数innodb_lock_wait_timeout的配置,判断是否需要进行timeout的操作,本文档介绍在出现锁等待时候的查看及分析处 ...

随机推荐

  1. 使用axios发送post请求,将JSON数据改为为form类型

    我的github(PS:希望star):https://github.com/thWinterSun/v-admin 通常前端通过POST请求向服务器端提交数据格式有4中,分别是"appli ...

  2. 如何合理的规划一次jvm性能调优

    https://blog.csdn.net/miracle_8/article/details/78347172 摘要: JVM性能调优涉及到方方面面的取舍,往往是牵一发而动全身,需要全盘考虑各方面的 ...

  3. [转载]彻底卸载oracleXE数据库服务器

    URL:http://www.2cto.com/database/201306/216182.html

  4. Python3.5+SQL+Prometheus+Grafana报表/监控

    参考资料: pymysql 单独获取表的栏位名称 pymysql返回数据为字典形式(key:value--列:值)   行列结合,作为prometheus_client的输出. 话不多说,直接上脚本. ...

  5. XE7 Unit scope names

    今天编译RM报表 7.0 for XE7 ,build设计时包,提示 {$IFDEF JPEG}, JPEG{$ENDIF} 没有找到 JPEG.DCU,这个应该是XE7自带. 后来 在项目选项里,编 ...

  6. Django(四)模板文件中的循环

    编辑views.py from django.shortcuts import render from django.shortcuts import HttpResponse #此行增加 # Cre ...

  7. 树状数组Lowbit用法

    刚学树状数组,看到这里的时候懵了.经过询问,发现,原来在程序运行时,数据用的都是补码,于是解决了 int Lowbit(x) { return x&(-x); } 如: x =1: 1 &am ...

  8. DevExpress v18.1新版亮点——ASP.NET Bootstrap篇(一)

    用户界面套包DevExpress v18.1日前终于正式发布,本站将以连载的形式为大家介绍各版本新增内容.本文将介绍了DevExpress ASP.NET Bootstrap v18.1 的新功能,快 ...

  9. CUDA ---- Dynamic Parallelism

    Dynamic Parallelism 到目前为止,所有kernel都是在host端调用,GPU的工作完全在CPU的控制下.CUDA Dynamic Parallelism允许GPU kernel在d ...

  10. 和不安全的Android说再见,Google为它添加新铠甲

    伴随着最近被曝出的Heartbleed漏洞,安全问题再次成为网络上的热点话题.虽然Android的安全性并没有外界传言的那样脆弱,但Google还是在继续为其增加防护措施.根据Android官方博客的 ...