这篇文章主要介绍“MySQL DDL锁表情况分析”，在日常操作中，相信很多人在MySQL DDL锁表情况分析问题上存在疑惑，小编查阅了各式资料，整理出简单好用的操作方法，希望对大家解答”MySQL DDL锁表情况分析”的疑惑有所帮助！接下来，请跟着小编一起来学习吧！

创新互联主营吴桥网站建设的网络公司,主营网站建设方案,APP应用开发,吴桥h5小程序定制开发搭建,吴桥网站营销推广欢迎吴桥等地区企业咨询

版本5.7.22，隔离级别RR

当DDL的表存在慢查询时，此时对该表做DDL，由于无法获得metadata锁，所以会等待该锁，造成锁表，后续DML操作全部进入等待状态。
session1：

session2：

session3：

session4：

tips:
select sleep(N) from t;表示查询t的时间为t中的行数*N，如下：

Before an online DDL operation can finish, it must wait for transactions that hold metadata locks on the table to commit or roll back. An online DDL operation may briefly require an exclusive metadata lock on the table during its execution phase, and always requires one in the final phase of the operation when updating the table definition. Consequently, transactions holding metadata locks on the table can cause an online DDL operation to block. The transactions that hold metadata locks on the table may have been started before or during the online DDL operation. A long running or inactive transaction that holds a metadata lock on the table can cause an online DDL operation to timeout.
在线DDL操作完成之前，必须等待持有表上的元数据锁的事务提交或回滚。在线DDL操作在执行阶段可能会短暂地需要表上的独占元数据锁，并且在更新表定义时总是在操作的最后阶段需要一个锁。因此，持有表上的元数据锁的事务可能导致在线DDL操作阻塞。表上持有元数据锁的事务可能在DDL在线操作之前或期间启动。在表上持有元数据锁的长时间运行或不活动的事务可能导致在线DDL操作超时。
https://dev.mysql.com/doc/refman/5.6/en/innodb-online-ddl-limitations.html
Online DDL and Metadata Locks
Online DDL operations can be viewed as having three phases:    DDL的在线操作可以分为三个阶段:

• Phase 1: Initialization  初始化
  In the initialization phase, the server determines how much concurrency is permitted during the operation, taking into account storage engine capabilities, operations specified in the statement, and user-specified ALGORITHM and LOCK options. During this phase, a shared upgradeable metadata lock is taken to protect the current table definition.
  在初始化阶段，服务器考虑存储引擎功能、语句中指定的操作以及用户指定的算法和锁选项，确定操作期间允许多少并发性。在此阶段，使用共享的可升级元数据锁来保护当前表定义。

• Phase 2: Execution
  In this phase, the statement is prepared and executed. Whether the metadata lock is upgraded to exclusive depends on the factors assessed in the initialization phase. If an exclusive metadata lock is required, it is only taken briefly during statement preparation.
  在这个阶段，语句被准备好并执行。元数据锁是否升级为exclusive取决于初始化阶段评估的因素。如果需要独占元数据锁，则只在语句准备期间进行短暂的锁定。

• Phase 3: Commit Table Definition 提交表定义
  In the commit table definition phase, the metadata lock is upgraded to exclusive to evict the old table definition and commit the new one. Once granted, the duration of the exclusive metadata lock is brief.
  在提交表定义阶段，将元数据锁升级为exclusive，以删除旧表定义并提交新表定义。一旦获得授权，独占元数据锁的持续时间很短。
  Due to the exclusive metadata lock requirements outlined above, an online DDL operation may have to wait for concurrent transactions that hold metadata locks on the table to commit or rollback. Transactions started before or during the DDL operation can hold metadata locks on the table being altered. In the case of a long running or inactive transaction, an online DDL operation can time out waiting for an exclusive metadata lock. Additionally, a pending exclusive metadata lock requested by an online DDL operation blocks subsequent transactions on the table.
  由于上面列出的独占元数据锁需求，在线DDL操作可能必须等待持有表上的元数据锁的并发事务提交或回滚。DDL操作之前或期间启动的事务可以在被修改的表上持有元数据锁。在长时间运行或不活动的事务的情况下，在线DDL操作可能会超时，等待独占元数据锁。此外，在线DDL操作请求的挂起的独占元数据锁会阻塞表上的后续事务。

到此，关于“MySQL DDL锁表情况分析”的学习就结束了，希望能够解决大家的疑惑。理论与实践的搭配能更好的帮助大家学习，快去试试吧！若想继续学习更多相关知识，请继续关注创新互联网站，小编会继续努力为大家带来更多实用的文章！

网页题目：MySQLDDL锁表情况分析
分享地址：http://kswjz.com/article/iegpoi.html