… data will be a very IO intense operation (redo logs, binlogs, etc) as well further polluting the buffer pool. Enter Xtrabackup…_old Make sure that the files are owned by mysql: chown mysql:mysql /var/lib/mysql/orig_old/* For each table, run: ALTER TABLE…_SCHEMA.TABLES WHERE TABLE_SCHEMA=’orig’ AND ENGINE=’InnoDB’; EOF mysql -N -B <<'EOF' > import-ddl.sql SELECT CONCAT(‘ALTER TABLE…
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
… it is usually very tedious and that proper recording of binlog file/binlog position needs to be done with care if you… try! # For s0,s1, s3, s4 mysql> stop slave; mysql> change master to master_port=10002; mysql> start slave; # And then check the… course, but very poor in my opinion: look for the binlog file/position of the last executed event and use mysqlbinlog…
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 21, 2013 By 8 Comments
…-only. However, “at the same time” means “at the same binlog position”, so you can perfectly restart the servers one by… not on slave #2: # slave #1 mysql> change master to master_auto_position = 1; mysql> start slave; and let’s create a… slave status\G [...] Auto_Position: 1 -> GTID-based positioning # Slave #2 mysql> show slave status\G [...] Auto_Position: 0 -> File-based positioning Conclusion…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 27, 2013 By 8 Comments
You can replicate from MySQL 5.6 to MariaDB 10.0 or vice versa. You … to use the GTID features to automatically pick the correct binlog position when switching to a new master. Old-style replication… MariaDB compatible without merging all of the crap that is MySQL 5.6 global transaction ID, I would very much like…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
June 10, 2013 By 8 Comments
It may not be easy to simply switch from regular MySQL replication to using replication using GTIDs 1. Temporary tables – CREATE… engine for the respective table on master databases. Also, if BINLOG_FORMAT is not consistent on master/slave db. 3. CREATE…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
… (and in my opinion bad) part of the design of MySQL 5.6 global transaction ID. In general, there is no… executed events is needed. And using mysqlbinlog to apply a binlog from a different server from a specific point does not…
Post: Percona XtraBackup 2.1.0 for MySQL beta now available
April 22, 2013 By Leave a Comment
… following: New Features: Percona XtraBackup has implemented basic support for MySQL 5.6, Percona Server 5.6 and MariaDB 10.0… fixed #1116177. innobackupex is using SHOW MASTER STATUS to obtain binlog file and position. This could trigger a bug if the… slave in replication) and binlog information wasn’t available. Fixed by not creating xtrabackup_binlog_info file when binlog isn’t available. Bug…
Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 1, 2013 By 10 Comments
Galera/Percona XtraDB Cluster (PXC) for MySQL is a hot thing right now and some users jump … because before Galera can create writesets for the replicated events, binlog events must be generated for the transactions first. Under normal… be good if your async master can use ROW based binlog format as well to achieve better consistency, if you have…
Post: Announcing Percona XtraBackup 2.1.1 GA
May 15, 2013 By Leave a Comment
…. innobackupex now uses Perl’s DBD::MySQL package for server communication instead of spawning the MySQL command line client. Support for InnoDB… slave in replication) and binlog information wasn’t available. Fixed by not creating xtrabackup_binlog_info file when binlog isn’t available. Bug…
Post: How to create a new (or repair a broken) GTID based slave with Percona XtraBackup
May 9, 2013 By 3 Comments
… will be a file with the name xtrabackup_binlog_info: # cat xtrabackup_binlog_info mysql-bin.000002 1232 c777888a-b6df-11e2-a604-080027635ef5… also printed by innobackupex after backup is taken: innobackupex: MySQL binlog position: filename ‘mysql-bin.000002′, position 1232, gtid_executed c777888a-b6df-11e2…
