pt-online-schema-change truncates recipient tables in XtraDB Cluster with Galera
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi,
I have a 3-node Percona XtraDB Cluster with Galera - 5.5.17-22.1-log with wsrep_OSU_
Was testing pt-online-
From node1:
mysql> select count(*) from n126db1.t1;
+----------+
| count(*) |
+----------+
| 7417938 |
+----------+
1 row in set (1.62 sec)
(This count matches on node2 and node3).
./pt-online-
# 2012-02-08T18:01:02 ./pt-online-
Enter password:
# 2012-02-08T18:01:06 USE `n126db1`
# 2012-02-08T18:01:06 Alter table t1 using temporary table __tmp_t1
# 2012-02-08T18:01:06 Checking if table t1 can be altered
# 2012-02-08T18:01:06 SHOW TRIGGERS FROM `n126db1` LIKE 't1'
# 2012-02-08T18:01:06 Table t1 can be altered
# 2012-02-08T18:01:06 Chunk column id, index PRIMARY
# 2012-02-08T18:01:06 Chunked table t1 into 7416 chunks
# 2012-02-08T18:01:06 Starting online schema change
# 2012-02-08T18:01:06 CREATE TABLE `n126db1`
# 2012-02-08T18:01:06 ALTER TABLE `n126db1`
# 2012-02-08T18:01:06 Shared columns: id, hostname, port, instime, c5
# 2012-02-08T18:01:06 Calling OSCCaptureSync:
# 2012-02-08T18:01:06 CREATE TRIGGER mk_osc_del AFTER DELETE ON `n126db1`.`t1` FOR EACH ROW DELETE IGNORE FROM `n126db1`
# 2012-02-08T18:01:06 CREATE TRIGGER mk_osc_upd AFTER UPDATE ON `n126db1`.`t1` FOR EACH ROW REPLACE INTO `n126db1`
# 2012-02-08T18:01:06 CREATE TRIGGER mk_osc_ins AFTER INSERT ON `n126db1`.`t1` FOR EACH ROW REPLACE INTO `n126db1`
# 2012-02-08T18:01:07 Calling CopyRowsInsertS
Copying rows: 15% 02:40 remain
Copying rows: 33% 02:00 remain
Copying rows: 51% 01:26 remain
Copying rows: 68% 00:54 remain
Copying rows: 85% 00:24 remain
# 2012-02-08T18:04:01 Calling OSCCaptureSync:
# 2012-02-08T18:04:01 Renaming tables
# 2012-02-08T18:04:01 RENAME TABLE `n126db1`.`t1` TO `n126db1`
# 2012-02-08T18:04:01 Original table t1 renamed to __old_t1
# 2012-02-08T18:04:01 Calling CopyRowsInsertS
# 2012-02-08T18:04:01 Calling OSCCaptureSync:
# 2012-02-08T18:04:01 DROP TRIGGER IF EXISTS `n126db1`
# 2012-02-08T18:04:01 DROP TRIGGER IF EXISTS `n126db1`
# 2012-02-08T18:04:01 DROP TRIGGER IF EXISTS `n126db1`
# 2012-02-08T18:04:01 DROP TABLE `n126db1`
# 2012-02-08T18:04:02 ./pt-online-
PTDEBUG output file is attached from a second test - row count is 2 million less and column name being added was different than above (c11).
PTDEBUG=1 ./pt-online-
Thanks
Patrick
tags: | added: pt-online-schema-change risk |
tags: | added: galera xtradb-cluster |
Changed in percona-toolkit: | |
status: | New → Triaged |
Changed in percona-toolkit: | |
assignee: | Daniel Nichter (daniel-nichter) → nobody |
status: | In Progress → Triaged |
I don't think it's clear that this tool is the right approach for schema changes in Galera/XtraDB Cluster.