pt-online-schema-change的实现原理

pt-online-schema-change用于MySQL的在线DDL。

下面结合官方文档和general log来分析其实现原理。

测试表

mysql> show create table t2\G

*************************** 1. row ***************************

       Table: t2

Create Table: CREATE TABLE `t2` (

  `id` int(11) NOT NULL AUTO_INCREMENT,

  PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=1005764 DEFAULT CHARSET=utf8

1 row in set (0.19 sec)

该表中只有1列，id，自增主键。

其中，表中已经存在一部分数据

mysql> select count(*) from t2;

+----------+

| count(*) |

+----------+

|  1005763 |

+----------+

1 row in set (0.31 sec)

利用pt-online-schema-change对该表新增一列

# pt-online-schema-change --execute --alter "ADD COLUMN c1 DATETIME" D=test,t=t2

Found 2 slaves:

  test

  hbase

Will check slave lag on:

  test

  hbase

Operation, tries, wait:

  analyze_table, 10, 1

  copy_rows, 10, 0.25

  create_triggers, 10, 1

  drop_triggers, 10, 1

  swap_tables, 10, 1

  update_foreign_keys, 10, 1

Altering `test`.`t2`...

Creating new table...

CREATE TABLE `test`.`_t2_new` (

  `id` int(11) NOT NULL AUTO_INCREMENT,

  PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=1005764 DEFAULT CHARSET=utf8

Created new table test._t2_new OK.

Waiting forever for new table `test`.`_t2_new` to replicate to test...

Altering new table...

ALTER TABLE `test`.`_t2_new` ADD COLUMN c1 DATETIME

Altered `test`.`_t2_new` OK.

2016-11-21T12:49:18 Creating triggers...

CREATE TRIGGER `pt_osc_test_t2_del` AFTER DELETE ON `test`.`t2` FOR EACH ROW DELETE IGNORE FROM `test`.`_t2_new` WHERE `test`.`_t2_ne

w`.`id` <=> OLD.`id`CREATE TRIGGER `pt_osc_test_t2_upd` AFTER UPDATE ON `test`.`t2` FOR EACH ROW REPLACE INTO `test`.`_t2_new` (`id`) VALUES (NEW.`id`)

CREATE TRIGGER `pt_osc_test_t2_ins` AFTER INSERT ON `test`.`t2` FOR EACH ROW REPLACE INTO `test`.`_t2_new` (`id`) VALUES (NEW.`id`)

2016-11-21T12:49:18 Created triggers OK.

2016-11-21T12:49:18 Copying approximately 1005075 rows...

INSERT LOW_PRIORITY IGNORE INTO `test`.`_t2_new` (`id`) SELECT `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= ?)) AND (

(`id` <= ?)) LOCK IN SHARE MODE /*pt-online-schema-change 2352 copy nibble*/SELECT /*!40001 SQL_NO_CACHE */ `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= ?)) ORDER BY `id` LIMIT ?, 2 /*next chun

k boundary*/Copying `test`.`t2`:  40% 00:44 remain

Copying `test`.`t2`:  82% 00:12 remain

2016-11-21T12:50:31 Copied rows OK.

2016-11-21T12:50:31 Analyzing new table...

2016-11-21T12:50:32 Swapping tables...

RENAME TABLE `test`.`t2` TO `test`.`_t2_old`, `test`.`_t2_new` TO `test`.`t2`

2016-11-21T12:50:35 Swapped original and new tables OK.

2016-11-21T12:50:35 Dropping old table...

DROP TABLE IF EXISTS `test`.`_t2_old`

2016-11-21T12:50:36 Dropped old table `test`.`_t2_old` OK.

2016-11-21T12:50:36 Dropping triggers...

DROP TRIGGER IF EXISTS `test`.`pt_osc_test_t2_del`;

DROP TRIGGER IF EXISTS `test`.`pt_osc_test_t2_upd`;

DROP TRIGGER IF EXISTS `test`.`pt_osc_test_t2_ins`;

2016-11-21T12:50:36 Dropped triggers OK.

Successfully altered `test`.`t2`.

查看general log中的输出

161017 11:22:56     1052 Connect    root@localhost on test

         1052 Query    set autocommit=1

         1052 Query    SHOW VARIABLES LIKE 'innodb\_lock_wait_timeout'

         1052 Query    SET SESSION innodb_lock_wait_timeout=1

         1052 Query    SHOW VARIABLES LIKE 'lock\_wait_timeout'

         1052 Query    SET SESSION lock_wait_timeout=60

         1052 Query    SHOW VARIABLES LIKE 'wait\_timeout'

         1052 Query    SET SESSION wait_timeout=10000

         1052 Query    SELECT @@SQL_MODE

         1052 Query    SET @@SQL_QUOTE_SHOW_CREATE = 1/*!40101, @@SQL_MODE='NO_AUTO_VALUE_ON_ZERO,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION'*/

         1052 Query    SELECT @@server_id /*!50038 , @@hostname*/

         1053 Connect    root@localhost on test

         1053 Query    set autocommit=1

         1053 Query    SHOW VARIABLES LIKE 'innodb\_lock_wait_timeout'

         1053 Query    SET SESSION innodb_lock_wait_timeout=1

         1053 Query    SHOW VARIABLES LIKE 'lock\_wait_timeout'

         1053 Query    SET SESSION lock_wait_timeout=60

         1053 Query    SHOW VARIABLES LIKE 'wait\_timeout'

         1053 Query    SET SESSION wait_timeout=10000

         1053 Query    SELECT @@SQL_MODE

         1053 Query    SET @@SQL_QUOTE_SHOW_CREATE = 1/*!40101, @@SQL_MODE='NO_AUTO_VALUE_ON_ZERO,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION'*/

         1053 Query    SELECT @@server_id /*!50038 , @@hostname*/

上述主要是设置会话的变量信息，包括innodb_lock_wait_timeout，wait_timeout和SQL_QUOTE_SHOW_CREATE。

         1052 Query    SHOW VARIABLES LIKE 'wsrep_on'

         1052 Query    SHOW VARIABLES LIKE 'version%'

         1052 Query    SHOW ENGINES

         1052 Query    SHOW VARIABLES LIKE 'innodb_version'

         1052 Query    SHOW VARIABLES LIKE 'innodb_stats_persistent'

         1052 Query    SELECT @@SERVER_ID

         1052 Query    SHOW GRANTS FOR CURRENT_USER()

         1052 Query    SHOW FULL PROCESSLIST

         1052 Query    SHOW SLAVE HOSTS

         1052 Query    SHOW GLOBAL STATUS LIKE 'Threads_running'

         1052 Query    SHOW GLOBAL STATUS LIKE 'Threads_running'

         1052 Query    SELECT CONCAT(@@hostname, @@port)

         1052 Query    SHOW TABLES FROM `test` LIKE 't2'

         1052 Query    SHOW TRIGGERS FROM `test` LIKE 't2'

         1052 Query    /*!40101 SET @OLD_SQL_MODE := @@SQL_MODE, @@SQL_MODE := '', @OLD_QUOTE := @@SQL_QUOTE_SHOW_CREATE, @@SQL_QUOTE_SHOW_CREATE := 1 */

         1052 Query    USE `test`

         1052 Query    SHOW CREATE TABLE `test`.`t2`

         1052 Query    /*!40101 SET @@SQL_MODE := @OLD_SQL_MODE, @@SQL_QUOTE_SHOW_CREATE := @OLD_QUOTE */

         1052 Query    EXPLAIN SELECT * FROM `test`.`t2` WHERE 1=1

         1052 Query    SELECT table_schema, table_name FROM information_schema.key_column_usage WHERE referenced_table_schema='test' AND referenced_table_name='t2'

         1052 Query    SHOW VARIABLES LIKE 'wsrep_on'

         1052 Query    /*!40101 SET @OLD_SQL_MODE := @@SQL_MODE, @@SQL_MODE := '', @OLD_QUOTE := @@SQL_QUOTE_SHOW_CREATE, @@SQL_QUOTE_SHOW_CREATE := 1 */

解释：

1. 查看参数变量，当前用户的权限，slave的信息，会话变量

2. 确认t2是否存在，t2上是否有触发器

3. 查看执行计划

4. 查看是否t2表是否被其它表外键关联。

           39 Query    USE `test`

           39 Query    SHOW CREATE TABLE `test`.`t2`

           39 Query    /*!40101 SET @@SQL_MODE := @OLD_SQL_MODE, @@SQL_QUOTE_SHOW_CREATE := @OLD_QUOTE */

           39 Query    CREATE TABLE `test`.`_t2_new` (

  `id` int(11) NOT NULL AUTO_INCREMENT,

  PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=1005764 DEFAULT CHARSET=utf8

161121 12:49:18       39 Query    ALTER TABLE `test`.`_t2_new` ADD COLUMN c1 DATETIME

           39 Query    /*!40101 SET @OLD_SQL_MODE := @@SQL_MODE, @@SQL_MODE := '', @OLD_QUOTE := @@SQL_QUOTE_SHOW_CREATE, @@SQL_QUOTE_SHOW_CREATE := 1 */

           39 Query    USE `test`

           39 Query    SHOW CREATE TABLE `test`.`_t2_new`

           39 Query    /*!40101 SET @@SQL_MODE := @OLD_SQL_MODE, @@SQL_QUOTE_SHOW_CREATE := @OLD_QUOTE */

           39 Query    CREATE TRIGGER `pt_osc_test_t2_del` AFTER DELETE ON `test`.`t2` FOR EACH ROW DELETE IGNORE FROM `test`.`_t2_new` WHERE `test`.`_t2_new`.`id` <=> OLD.`id`

           39 Query    CREATE TRIGGER `pt_osc_test_t2_upd` AFTER UPDATE ON `test`.`t2` FOR EACH ROW REPLACE INTO `test`.`_t2_new` (`id`) VALUES (NEW.`id`)

           39 Query    CREATE TRIGGER `pt_osc_test_t2_ins` AFTER INSERT ON `test`.`t2` FOR EACH ROW REPLACE INTO `test`.`_t2_new` (`id`) VALUES (NEW.`id`)

解释：

1. 根据目标表结构创建一张新表。

2. 对新表添加字段，可以看出pt-online-shema-change对表结构进行变更依赖的还是MySQL自身的Online DDL。

3. 针对目标表创建三个触发器，DELETE，UPDATE和INSERT，因为REPLACE操作只有在主键或唯一索引存在的情况下才有意义，这也就解释了为什么目标表上要有主键或唯一索引。

           39 Query    EXPLAIN SELECT * FROM `test`.`t2` WHERE 1=1

           39 Query    SELECT /*!40001 SQL_NO_CACHE */ `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) ORDER BY `id` LIMIT 1 /*first lower boundary*/

           39 Query    SELECT /*!40001 SQL_NO_CACHE */ `id` FROM `test`.`t2` FORCE INDEX (`PRIMARY`) WHERE `id` IS NOT NULL ORDER BY `id` LIMIT 1 /*key_len*/

           39 Query    EXPLAIN SELECT /*!40001 SQL_NO_CACHE */ * FROM `test`.`t2` FORCE INDEX (`PRIMARY`) WHERE `id` >= '' /*key_len*/

           39 Query    EXPLAIN SELECT /*!40001 SQL_NO_CACHE */ `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) ORDER BY `id` LIMIT 999, 2 /*next chunk boundary*/

           39 Query    SELECT /*!40001 SQL_NO_CACHE */ `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) ORDER BY `id` LIMIT 999, 2 /*next chunk boundary*/

           39 Query    EXPLAIN SELECT `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) AND ((`id` <= '')) LOCK IN SHARE MODE /*explain pt-online-schema-change 2352 copy nibble*/

           39 Query    INSERT LOW_PRIORITY IGNORE INTO `test`.`_t2_new` (`id`) SELECT `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) AND ((`id` <= '')) LOCK IN SHARE MODE /*pt-online-schema-change 2352 copy nibble*/

           39 Query    SHOW WARNINGS

           39 Query    SELECT @@SERVER_ID

           39 Query    SHOW GRANTS FOR CURRENT_USER()

           39 Query    SHOW FULL PROCESSLIST

           39 Query    SELECT @@SERVER_ID

           39 Query    SHOW GRANTS FOR CURRENT_USER()

           39 Query    SHOW FULL PROCESSLIST

161121 12:49:20       39 Query    SELECT 'pt-online-schema-change keepalive'

161121 12:49:21       39 Query    SELECT @@SERVER_ID

           39 Query    SHOW GRANTS FOR CURRENT_USER()

           39 Query    SHOW FULL PROCESSLIST

           39 Query    SHOW GLOBAL STATUS LIKE 'Threads_running'

           39 Query    EXPLAIN SELECT /*!40001 SQL_NO_CACHE */ `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) ORDER BY `id` LIMIT 28516, 2 /*next chunk boundary*/

           39 Query    SELECT /*!40001 SQL_NO_CACHE */ `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) ORDER BY `id` LIMIT 28516, 2 /*next chunk boundary*/

           39 Query    EXPLAIN SELECT `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) AND ((`id` <= '')) LOCK IN SHARE MODE /*explain pt-online-schema-change 2352 copy nibble*/

           39 Query    INSERT LOW_PRIORITY IGNORE INTO `test`.`_t2_new` (`id`) SELECT `id` FROM `test`.`t2` FORCE INDEX(`PRIMARY`) WHERE ((`id` >= '')) AND ((`id` <= '')) LOCK IN SHARE MODE /*pt-online-schema-change 2352 copy nibble*/

解释：

上述输出只包含两个chunk的选择。其它chunk的选择基本相同。

1. SHOW GLOBAL STATUS LIKE 'Threads_running'用于监控当前的系统负载。

2. 可以看出pt-online-schema-change是以chunk为单位进行目标表数据的拷贝。

3. 在拷贝的过程中，对目标表的相关记录加了共享锁，此时，会堵塞客户端对这些记录的DML操作。

           39 Query    ANALYZE TABLE `test`.`_t2_new` /* pt-online-schema-change */

161121 12:50:32       39 Query    RENAME TABLE `test`.`t2` TO `test`.`_t2_old`, `test`.`_t2_new` TO `test`.`t2`

161121 12:50:35       39 Query    DROP TABLE IF EXISTS `test`.`_t2_old`

161121 12:50:36       39 Query    DROP TRIGGER IF EXISTS `test`.`pt_osc_test_t2_del`

           39 Query    DROP TRIGGER IF EXISTS `test`.`pt_osc_test_t2_upd`

           39 Query    DROP TRIGGER IF EXISTS `test`.`pt_osc_test_t2_ins`

           39 Query    SHOW TABLES FROM `test` LIKE '\_t2\_new'

161121 12:50:37       40 Quit

           39 Quit

解释：

1. 在完成数据的拷贝后，会对新表执行ANALYZE操作，这样，可及时更新新表的统计信息。

官档的解释如下：

This circumvents a potentially serious issue related to InnoDB optimizer statistics. If the table being alerted is

busy and the tool completes quickly, the new table will not have optimizer statistics after being swapped. This

can cause fast, index-using queries to do full table scans until optimizer statistics are updated (usually after 10

seconds). If the table is large and the server very busy, this can cause an outage.

2. 对目标表和新表进行RENAME操作。

3. 删除原来的目标表

4. 删除触发器。

pt-online-schema-change的实现原理的更多相关文章

schema change + ogg 变更手册
Check OGG until no data queuing in replication process:testRO:a)login test5 –l oggmgrb)oggc)#ggsci ...
Online Schema Change for MySQL
It is great to be able to build small utilities on top of an excellent RDBMS. Thank you MySQL. This ...
AppBoxFuture(四). 随需而变-Online Schema Change
需求变更是信息化过程中的家常便饭,而在变更过程中如何尽可能小的影响在线业务是比较头疼的事情.举个车联网监控的例子:原终端设备上传车辆的经纬度数据,新的终端设备支持同时上传速度数据,而旧的车辆状态表 ...
Online, Asynchronous Schema Change in F1
F1: A Distributed SQL Database That Scales http://disksing.com/understanding-f1-schema-change ma ...
MySQL OSC(在线更改表结构)原理
1 OSC介绍在我们的数据库操作中,更改表结构是一个常见的操作,而当我们的表数据量非常大时,我们更改表结构的时间是非常的长,并且在跟改期间,会生成一个互斥锁,阻塞对整个表的所有操作,这样,对于我们 ...
Online Schema Upgrade in MySQL Galera Cluster using TOI Method
http://severalnines.com/blog/online-schema-upgrade-mysql-galera-cluster-using-toi-method As a fo ...
OSC的原理
OSC是Online Schema Change简写,即在线架构改变.其实现步骤: 1. init,即初始化阶段,会对创建的表做一些验证工作,如检查表是否有主键,是否存在触发器或者外键等.2. cre ...
Schema 与数据类型优化
这是<高性能 MySQL(第三版)>第四章<Schema 与数据类型优化>的读书笔记. 1. 选择优化的数据类型数据类型的选择原则: 越小越好:选择满足需求的最小类型.注意, ...
MongoDB 变更流（Change Stream）介绍
1. 什么是Change Stream Change Stream 是MongoDB用于实现变更追踪的解决方案,类似于关系数据库的触发器,但原理不完全相同: | | Change Stream | 触 ...
iDB是如何运转的一
郑昀创建于2015/12/2 最后更新于2015/12/4 关键词:数据库,MySQL,自动化运维,DDL,DML,SQL审核,备份,回滚,Inception,osc 提纲: 普通DBA和文艺DBA ...

随机推荐

Sql2008R2的一个补丁BUG-大家使用时请注意
我们都知道Sqlserver为了提高并发,允许乐观隔离级别(读提交快照,快照)以便读与写之间不阻塞.这里有一个在Sqlserver2008R2 SP2 的热补丁(CU11)下RCSI(读提交快照)隔离 ...
Jmeter中自动重定向与跟随重定向的区别
一.重定向就是通过各种方法将各种网络请求重新定个方向转到其它位置. 二.我们在网站建设中,时常会遇到需要网页重定向的情况: 1.网站调整(如改变网页目录结构): 2.网页被移到一个新地址: 3.网页扩 ...
history历史记录控制
往往我们操作的每一条命令都会被机器记录下来,所有我们为了安全需要屏蔽掉某些敏感的操作命令. 设置linux默认的历史记录数: 临时生效: export HISTSIZE=5 history 永久生效 ...
python: 用pygments给markdown文档染色
首先你需要一个markdown解析器比如有常见的markdown和markdown2,其他的可以参考这个网站的评价我选择了mistune,自己继承写一个渲染的Renderer mistune的do ...
Python接口自动化--SSL 3
官方文档参考地址: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings 针对SSL Warnings,u ...
（二十）ArcGIS JS 加载WMTS服务（超图示例）
前言在前一篇中说到我们可以通过加载WMS服务解决用ArcGIS API加载超图发布的服务,但是WMS服务在加载效率上是低于切片服务的,加上超图的IServer,无力吐槽,所以,在加载速度的要求下,切 ...
命令行翻译推荐一个linux系统中可用的终端小程序
程序的github地址:https://github.com/fanbrightup/fanyi 使用起来非常简单,同时支持中英文互译甚至是整句. 步骤一:首先你需要安装node,参见我的node安装 ...
BZOJ3233:[AHOI2013]找硬币(DP)
Description 小蛇是金融部部长.最近她决定制造一系列新的货币.假设她要制造的货币的面值为x1,x2,x3… 那么x1必须为1,xb必须为xa的正整数倍(b>a).例如 1,5,125, ...
tomcat访问manager报404;server.xml中配置了Context path
<Context path="" docBase="crm" debug="0" reloadable="true" ...
DataGridView如何绑定DataRow对象集合
DataGridView对象是我们在进行Winform程序开发中经常使用的呈现数据的控件,而数据则是通过DataSource这个Property来设置的.根据MSDN的说明,DataGridView对 ...

pt-online-schema-change的实现原理

pt-online-schema-change的实现原理的更多相关文章

随机推荐

热门专题